allow eclipse-score-bot to push directly to main branch

[AlexanderLanin]

Co-authored-by: Maximilian Sören Pollak maximilian.pollak@qorix.com

[AlexanderLanin]

Verified string on internal otterdog instance. It's #OrganizationAdmin

[eclipse-otterdog]

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 be fulfilled for auto-merging to be available:

• valid configuration
• approved by a project lead
• does not require any secrets
• does not update settings only accessible via the GitHub Web UI
• does not remove any resource

Otterdog commands and options

You can trigger otterdog actions by commenting on this PR:

• /otterdog team-info checks the team / org membership for the PR author
• /otterdog validate validates the configuration change
• /otterdog validate info validates the configuration change, printing also validation infos
• /otterdog check-sync checks if the base ref is in sync with live settings
• /otterdog merge merges and applies the changes if the PR is eligible for auto-merging (only accessible for the author)
• /otterdog done notifies the self-service bot that a required manual apply operation has been performed (only accessible for members of the admin team)
• /otterdog apply re-apply a previously failed attempt (only accessible for members of the admin team)

[eclipse-otterdog]

The author (AlexanderLanin) of this PR is associated with this organization in the role of MEMBER.

Additionally, AlexanderLanin is a member of the following teams:

• automotive-score-committers

• automotive-score-security

• cft-orchestration

• cft-feo

• infrastructure-maintainers

• codeowner-reference_integration

[FScholPer]

Whats the usecase ?

[AlexanderLanin]

Whats the usecase ?

sorry, not sure where it got lost. We changed bazel_registry to push directly to main branch, as the automatically created PRs do not add any value. There is absolutely no reason to ever reject such an automated PR. They just add delays. Maybe we should not have put the actual data on the main branch, but thats how it is at the moment. Anyway as we don't do any review anyway, and the PRs are just delays, we got rid of them. However now the bazel_registry is not being updated, as the eclipse-score-bot cannot write directly to main. We accidentally prevented that with the previously configured repository rule. This PR makes a careful local only adjustment, where only the repository rule for bazel_registry is fixed and allows organization owners to push directly to main.

[AlexanderLanin]

/otterdog merge

[eclipse-otterdog]

Warning

This pull request cannot be auto-merged via /otterdog merge

• author is not eligible for merge without approvals, and it has not been checked whether the pull request has the required approvals

[kairoaraujo]

/otterdog merge

[eclipse-otterdog]

Warning

This pull request cannot be auto-merged via /otterdog merge

• pull request does not have the required approvals, and the author is not eligible for merge without approvals

[AlexanderLanin]

/otterdog merge

[eclipse-otterdog]

Warning

This pull request cannot be auto-merged via /otterdog merge

• pull request does not have the required approvals, and the author is not eligible for merge without approvals

[MaximilianSoerenPollak]

@kairoaraujo Could you merge this PR? Seems that it gotten out of sync again.

[eclipse-otterdog]

Please find below the validation of the requested configuration changes:

Diff for f5d5834

Project automotive.score[github_id=eclipse-score]
  there have been 38 validation infos, enable verbose output to display them.

  
!   repo_ruleset[name="main", repository=bazel_registry] {
!     bypass_actors           = [
+      "#OrganizationAdmin"
!     ]
!     include_refs            = [
!       "refs/heads/main" -> "~DEFAULT_BRANCH"
!     ]
!     requires_linear_history = false -> true
!   }
  
  Plan: 0 to add, 3 to change, 0 to delete.

[eclipse-otterdog]

Note

The current configuration is out-of-sync with the live settings:

Diff to live settings

Project automotive.score[github_id=eclipse-score]
  there have been 38 validation infos, enable verbose output to display them.

  
!   repository[name="docs-as-code"] {
!     code_scanning_default_query_suite = "extended" -> "default"
!   }

-  remove environment[name="copilot", repository=logging] {
-    deployment_branch_policy = "all"
-    name                     = "copilot"
-    reviewers                = []
-    wait_timer               = 0
-  }

-  remove environment[name="copilot", repository=inc_someip_gateway] {
-    deployment_branch_policy = "all"
-    name                     = "copilot"
-    reviewers                = []
-    wait_timer               = 0
-  }

  
!   repository[name="more-disk-space"] {
!     code_scanning_default_languages = [
-      "javascript"
+      "javascript-typescript"
-      "typescript"
!     ]
!   }
  
  Plan: 0 to add, 2 to change, 2 to delete.