[eliorerz]

The apply of the previous change (Let ci-duty bypass branch protections with its role) failed:

Error updating GitHub organization repository role (osac-project/ci-maintainer): PATCH .../custom-repository-roles/103023: 422 Description cannot be longer than 152 characters

The description I extended with the bypass was 161 characters. This shortens it to 126 (Write, plus Actions secrets, variables, environments, settings and runners, merge queue priority, and branch protection bypass). Nothing else changes: the role, its permissions (including bypass_branch_protection) and the README stay as they are. Until this is merged and applied, every pending Terraform change of every repository waits behind the failed apply (it filed an issue). Merging applies it (apply.yaml runs on a push to main that touches *.tf).

The role itself was not updated by the failed apply, so the force-merge checkbox for ci-duty does not appear yet; it will once this is applied.

Not run locally: tofu is not installed here; the change is one string and the failed run's TF Init and Validate steps passed with the longer one.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML; Path: .coderabbit.yaml
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 4146865c-d87e-4da1-84c4-1b0723a0a669

📥 Commits

Reviewing files that changed from the base of the PR and between a0ca085 and 4d6bf40.

📒 Files selected for processing: 1

• organization.tf

+---------------------+
| I've git the power! |
+---------------------+
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

_{Comment @coderabbitai help to get the list of available commands.}