-
Notifications
You must be signed in to change notification settings - Fork 574
Add validation for ADR labels in PRs #5315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
docs/ADRTags.md
Outdated
| @@ -0,0 +1,5 @@ | |||
| # Update the PR validation workflow to require ADR labeling. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this just be in https://github.com/microsoft/fhir-server/blob/main/SquashMergeRequirements.md?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
This makes sense Co-authored-by: Brendan Kowitz <[email protected]>
…m/microsoft/fhir-server into personal/rajitha/add-tags-for-adr
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| 1. Tag the PR with **Schema Version backward compatible** or **Schema Version backward incompatible** or **Schema Version unchanged** if this adds/updates Sql script which is/is not backward compatible with the code. | ||
| 1. Include a user friendly, 1-2 sentence in the Squash/Merge **description** wrapped at 72 characters | ||
| 1. Note if it **addresses a GitHub issue and/or a VSTS item** in the Squash/Merge description (i.e. #1234 or AB#12345) | ||
| 1. Tag the PR with **ADR-Included or **No-ADR, indicating whether documentation for the change is provided or not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these for bolded syntax?
| 1. Tag the PR with **ADR-Included or **No-ADR, indicating whether documentation for the change is provided or not. | |
| 1. Tag the PR with **ADR-Included** or **No-ADR**, indicating whether documentation for the change is provided or not. |
Description
This pull request updates the PR validation workflow to include one of the following labels: ADR-Included or No-ADR, indicating whether documentation for the change is provided or not.
Related issues
Addresses [issue 180231].
Testing
Describe how this change was tested.
FHIR Team Checklist
Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)