Skip to content

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.

Sign up for GitHub

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

Open
rajithaalurims wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add validation for ADR labels in PRs #5315

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
874bb2b
Add validation for ADR labels in PRs
rajithaalurims Jan 7, 2026
6257ab0
Update .github/workflows/validate-prs.yml
rajithaalurims Jan 8, 2026
484662a
SquashMergeRequirements doc updated
rajithaalurims Jan 8, 2026
5ed0d0c
Merge branch 'personal/rajitha/add-tags-for-adr' of https://github.co…
rajithaalurims Jan 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/validate-prs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,12 @@ jobs:
errors += '- Tag the PR with **No-PaaS-breaking-change** or **PaaS-breaking-change** to indicate PaaS compatibility. \n';
}

if(labels.includes("ADR-Included") == false &&
labels.includes("No-ADR") == false) &&
excludeAuthors.includes(author) == false {
errors += '- Tag the PR with **No-ADR** or **ADR-Included** to indicate whether documentation for the change is provided or not. \n';
}

if(errors != "") {
core.setFailed(errors)
}
1 change: 1 addition & 0 deletions SquashMergeRequirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ When commiting your PR, please make sure to do these steps at Squash/Merge to as
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

@brendankowitz brendankowitz Jan 9, 2026

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.


Sometimes our changes will create breaking changes or may need a warning associated with them. If this is the case, take these additional steps:

Expand Down
Loading