Skip to content

Conversation

@gigamonster256
Copy link
Contributor

@gigamonster256 gigamonster256 commented Feb 3, 2026

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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

The following comment was made by an LLM, it may be inaccurate:

No duplicate PRs found

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.

1 participant