Skip to content
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.

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

[BUG][WEBSITE] Process dictates that main gets updated from stablization branches but there is no automated prevention #2564

Open
RoddieKieley opened this issue Jun 17, 2024 · 1 comment
Labels
sig/docs-community Categorizes an issue or PR as relevant to SIG Docs-Community.

Comments

@RoddieKieley
Copy link
Contributor

Describe the bug

In reviewing current main branch status it was noted that main was 77 commits ahead and 24 commits behind development. In theory and by process main should ever get updated when stabilization is merged during a release.

Are there settings or automation we can put in place for this restriction to help prevent this issue from reoccurring?

@RoddieKieley RoddieKieley added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 17, 2024
@ShaunaGordon
Copy link
Contributor

@RoddieKieley Did we get this taken care of enough to close this issue?

@ShaunaGordon ShaunaGordon added sig/docs-community Categorizes an issue or PR as relevant to SIG Docs-Community. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/docs-community Categorizes an issue or PR as relevant to SIG Docs-Community.
Projects
None yet
Development

No branches or pull requests

2 participants