Closed netomi closed 2 months ago
This is your friendly self-service bot.
Thank you for raising a pull request to update the configuration of your GitHub organization. You can manually add reviewers to this PR to eventually enable auto-merging.
The following conditions need to fulfilled for auto-merging to be available:
This is your friendly self-service bot. Please find below the validation of the requested configuration changes:
This is your friendly self-service bot. The current configuration is in-sync with the live settings. :rocket:
This is your friendly self-service bot. Please find below the validation of the requested configuration changes:
This is your friendly self-service bot. The current configuration is in-sync with the live settings. :rocket:
This is your friendly self-service bot. Please find below the validation of the requested configuration changes:
This is your friendly self-service bot. The current configuration is in-sync with the live settings. :rocket:
@mnonnenmacher this should be an equivalent ruleset for your existing branch protection rule but with support for a merge queue.
I did realize that the defaults for a ruleset and branch protection are slightly different, that makes the conversion a bit cumbersome. Will look into that, thats why I had to add some more properties as before as these are enabled by default for a ruleset atm.
Actually, now that merge queues are also supported by the ECA validation service, we can also re-add that status check.
This is your friendly self-service bot. Please find below the validation of the requested configuration changes:
This is your friendly self-service bot. The current configuration is in-sync with the live settings. :rocket:
This is your friendly self-service bot. Please find below the validation of the requested configuration changes:
This is your friendly self-service bot. The current configuration is in-sync with the live settings. :rocket:
the default config has been updated to be aligned with the default settings for a branch protection rule. Now the conversion should be much easier.
Furthermore, I grouped now settings related to requiring a pull request into an embedded object to make sense easier to understand and configure, similar to what has been done for merge queues.
/otterdog validate
This is your friendly self-service bot. Please find below the validation of the requested configuration changes:
/otterdog check-sync
This is your friendly self-service bot. The current configuration is in-sync with the live settings. :rocket:
This is your friendly self-service bot.
The following changes have been successfully applied:
Organization technology.apoapsis[id=eclipse-apoapsis]
- remove branch_protection_rule[pattern="main", repository="ort-server"] {
- allows_deletions = false
- allows_force_pushes = false
- blocks_creations = false
- bypass_force_push_allowances = []
- bypass_pull_request_allowances = []
- dismisses_stale_reviews = true
- is_admin_enforced = true
- lock_allows_fetch_and_merge = false
- lock_branch = false
- pattern = "main"
- require_last_push_approval = false
- required_approving_review_count = "1"
- required_status_checks = [
- "build"
- "build-ui"
- "commit-lint"
- "detekt-issues"
- "eslint"
- "integration-test"
- "prettier"
- "renovate-validation"
- "reuse-tool"
- "test"
- "website-test"
- "wrapper-validation"
- ],
- requires_code_owner_reviews = false
- requires_commit_signatures = false
- requires_conversation_resolution = false
- requires_deployments = false
- requires_linear_history = true
- requires_pull_request = true
- requires_status_checks = true
- requires_strict_status_checks = false
- restricts_pushes = false
- restricts_review_dismissals = false
- }
+ add repo_ruleset[name="main", repository="ort-server"] {
+ allows_creations = false
+ allows_deletions = false
+ allows_force_pushes = false
+ allows_updates = true
+ bypass_actors = []
+ enforcement = "active"
+ exclude_refs = []
+ include_refs = [
+ "refs/heads/main"
+ ],
+ name = "main"
+ required_merge_queue = {
+ build_concurrency = "5"
+ max_group_size = "5"
+ merge_method = "REBASE"
+ min_group_size = "1"
+ requires_all_group_entries_to_pass_required_checks = true
+ status_check_timeout = "60"
+ wait_time_for_minimum_group_size = "5"
+ }
+ required_pull_request = {
+ dismisses_stale_reviews = true
+ required_approving_review_count = "1"
+ requires_code_owner_review = false
+ requires_last_push_approval = false
+ requires_review_thread_resolution = false
+ }
+ required_status_checks = [
+ "build"
+ "build-ui"
+ "commit-lint"
+ "detekt-issues"
+ "eslint"
+ "integration-test"
+ "prettier"
+ "renovate-validation"
+ "reuse-tool"
+ "test"
+ "website-test"
+ "wrapper-validation"
+ ],
+ requires_commit_signatures = false
+ requires_deployments = false
+ requires_linear_history = true
+ requires_status_checks = true
+ requires_strict_status_checks = false
+ }
Applying changes:
Done.
Executed plan: 1 added, 0 changed, 1 deleted.
Merge Queue has been correctly applied:
the structuring of the settings also is much nicer with rulesets, backporting this to branch protection rules will be some work as we would need to adjust all existing configurations.
the structuring of the settings also is much nicer with rulesets, backporting this to branch protection rules will be some work as we would need to adjust all existing configurations.
To me there is no need to backport this if rulesets are the future anyway.
As discussed in https://github.com/eclipse-csi/otterdog/issues/86.