Skip to content

Conversation

@ktdreyer
Copy link
Contributor

@ktdreyer ktdreyer commented Jul 3, 2025

Our main branch has many CI fixes and improvements that we want to incorporate into our stable release branch. This will increase our confidence in CI results for backport PRs.

Sync our .github directory on release-v0.10 with what is in the main branch (commit beae7f1)

Our main branch has many CI fixes and improvements that we want to
incorporate into our stable release branch. This will increase our
confidence in CI results for backport PRs.

Sync our .github directory on release-v0.10 with what is in the main
branch (commit beae7f1)

Signed-off-by: Ken Dreyer <[email protected]>
@mergify mergify bot added CI/CD Affects CI/CD configuration release-branch ci-failure labels Jul 3, 2025
@ktdreyer ktdreyer changed the title update .github from main (commit beae7f14) Draft: update .github from main (commit beae7f14) Jul 3, 2025
@ktdreyer
Copy link
Contributor Author

ktdreyer commented Jul 3, 2025

I made a mistake in naming my work-in-progress branch release-v0.10-gh-actions-from-main for this PR. This name happens to match our branch protections rules in GitHub. Specifically, no one is allowed to force-push any branch named release-*:

image

As a result, I cannot update this PR 🤡

I will delete this branch and close this PR, and create a new one with a branch that does not run into this rule.

@ktdreyer ktdreyer closed this Jul 3, 2025
@ktdreyer ktdreyer deleted the release-v0.10-gh-actions-from-main branch July 3, 2025 16:04
@ktdreyer
Copy link
Contributor Author

ktdreyer commented Jul 3, 2025

For the record: I temporarily disabled the rule to allow me to delete this branch:

image

Then I deleted release-v0.10-gh-actions-from-main , and I re-enabled the rule again to protect release-*.

@ktdreyer
Copy link
Contributor Author

ktdreyer commented Jul 3, 2025

My new PR with a safer branch name is #637

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

Labels

CI/CD Affects CI/CD configuration ci-failure release-branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants