Source branch validation - #1161
Closed
CringeCursed wants to merge 4 commits into
Closed
Conversation
Member
Author
Member
Author
|
yappy 😀 |
Contributor
|
Originate from starlight-dev or are being PRed TO starlight-dev? If its the first I am never PRing again because I can't get that working. |
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Short description
Add GitHub Actions workflow to validate that PR branches are created from
starlight-devWhy we need to add this
This PR adds a new GitHub Actions workflow that enforces proper branch management by validating the source of pull request branches. The workflow uses git history analysis to ensure branches are properly derived from
starlight-dev.Technical implementation:
git merge-baseto find the common ancestor between the PR branch andstarlight-devstarlight-devstarlight-devHEADactions/github-scriptfetch-depth: 0to ensure full git history is available for accurate ancestry checkingThe strict ancestry checking ensures that branches haven't diverged from an old version of
starlight-devMedia (Video/Screenshots)
Checks
Changelog
🆑 Cringe_Cursed