feat(beta): allow commits on top of beta PRs #11924
Open
+10
−5
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.
any commits (CI or otherwise) on top of the authoritative beta PRs (ones with beta tag) would make tree hash mis-match and trigger a force push
the first commit relaxes this to allow the beta branch to remain as long as the beta branch history contains all beta PRs and is based on current dev branch
before:
only dev..beta_PRs
after:
allows dev..beta_PRs..extra_commits
the second commit takes advantage of this relaxation to apply nix-hash updates to the beta branch as needed
feel free to close if this is not the correct model for the beta branch
related: #11919