Skip to content

fix: correct domain reference in ADAE example comments (#163) - #164

Merged
bms63 merged 2 commits into
pharmaverse:mainfrom
LeonidasZhak:fix/adae-domain-typo
Oct 4, 2026
Merged

bms63 merged 2 commits into
pharmaverse:mainfrom
LeonidasZhak:fix/adae-domain-typo

Conversation

@LeonidasZhak

Copy link
Copy Markdown
Contributor

What

Corrects a comment typo in the ADAE example files where the domain reference was incorrectly set to VS (Vital Signs) instead of AE (Adverse Events).

Changes

  • adam/adae.qmd: Changed '# Join ADSL variables with VS' to '# Join ADSL variables with AE'
  • adam/adae.R: Changed '# Join ADSL variables with VS' to '# Join ADSL variables with AE'

Context

The ADAE example joins ADSL variables with the AE domain (adverse events), not the VS domain (vital signs). The ADVS example files correctly reference VS. This is a comment-only fix with no functional impact.

Fixes #163

The comment 'Join ADSL variables with VS' incorrectly references the VS
(Vital Signs) domain. Since this is the ADAE (Adverse Events) example,
the comment should reference the AE domain instead.

Fixes pharmaverse#163

@bms63 bms63 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the quick fix!!

@LeonidasZhak

Copy link
Copy Markdown
Contributor Author

Thanks again for the approval. I checked the outstanding CI result: Links, Style, and Spellcheck all pass. The only failure is in “Build & Deploy Website” at “Publish PR docs in a subdirectory”, where github-actions[bot] receives a repository write-permission 403.

Because that permission is controlled on the upstream workflow side, I can’t correct it from the fork. Could you advise whether the deployment failure can be ignored for this PR or re-run with the required permission? I’m happy to make any change if there is a patch-specific issue.

@LeonidasZhak

Copy link
Copy Markdown
Contributor Author

Following up once more on the website workflow question. The PR remains approved, and the only failing check I can see is the repository-side permission error in “Publish PR docs in a subdirectory.” Could a maintainer confirm whether that check is required for merge, or rerun it with the required permission? I have not found a patch-specific failure.

@bms63

bms63 commented Oct 4, 2026

Copy link
Copy Markdown
Collaborator

ah - this is due to forking the repo. all good. i will merge in and i made it so the forks bypass this action. probably should be a little stricter :)

@bms63
bms63 merged commit d35207a into pharmaverse:main Oct 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A very minor typo in example

2 participants