-
Notifications
You must be signed in to change notification settings - Fork 4
Temporarily Undo Read-Only Repos #54
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
base: main
Are you sure you want to change the base?
Conversation
|
Thank you for raising a pull request to update the configuration of your GitHub organization. The following conditions need to fulfilled for auto-merging to be available:
Otterdog commands and optionsYou can trigger otterdog actions by commenting on this PR:
|
|
Please find below the validation of the requested configuration changes: Diff for f5cb7baProject rt.jetty[github_id=jetty]
there have been 22 validation infos, enable verbose output to display them.
- remove repo_ruleset[name="read-only-branches", repository=jetty.project] {
- allows_creations = false
- allows_deletions = false
- allows_force_pushes = false
- allows_updates = false
- bypass_actors = []
- enforcement = "disabled"
- exclude_refs = []
- include_refs = [
- "refs/heads/jetty-9.4.x"
- "refs/heads/jetty-10.0.x"
- "refs/heads/jetty-11.0.x"
- ],
- name = "read-only-branches"
- required_merge_queue = null
- required_pull_request = {
- dismisses_stale_reviews = false
- required_approving_review_count = 2
- requires_code_owner_review = false
- requires_last_push_approval = false
- requires_review_thread_resolution = false
- }
- required_status_checks = {
- do_not_enforce_on_create = false
- status_checks = [
- "eclipse-eca-validation:eclipsefdn/eca"
- ],
- strict = false
- }
- requires_commit_signatures = false
- requires_deployments = false
- requires_linear_history = false
- target = "branch"
- }
Plan: 0 to add, 0 to change, 1 to delete. |
| }, | ||
| }, | ||
| orgs.newRepoRuleset('read-only-branches') { | ||
| enforcement: "disabled", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure to understand as this enforcement should be disabled see #53
especially this comment #53 (comment)
I'm a bit confused why we would need this?
This is a temporary change, that will likely be undone once Jan 1, 2026 hits, and we start our new EOL branch process.
For now, we need access to these branches.