Skip to content

Conversation

@rajithaalurims
Copy link
Contributor

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.

  • This ensures that every change is accompanied by its rationale and details, making it easier to track the context behind modifications in the future without scrambling to figure out who made the change and why.

Related issues

Addresses [issue 180231].

Testing

Describe how this change was tested.

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@rajithaalurims rajithaalurims added this to the CY25Q3/2Wk13 milestone Jan 7, 2026
@rajithaalurims rajithaalurims requested a review from a team as a code owner January 7, 2026 18:03
@rajithaalurims rajithaalurims added Build No-PaaS-breaking-change ADR-Included ADR Included in the PR and removed ADR-Included ADR Included in the PR labels Jan 7, 2026
docs/ADRTags.md Outdated
@@ -0,0 +1,5 @@
# Update the PR validation workflow to require ADR labeling.
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@rajithaalurims
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

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.
Copy link
Member

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?

Suggested change
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants