Skip to content

fix: provision every documented autorelease environment - #52

Merged
loadinglucian merged 2 commits into
mainfrom
fix/provision-documented-environments
Aug 2, 2026
Merged

fix: provision every documented autorelease environment#52
loadinglucian merged 2 commits into
mainfrom
fix/provision-documented-environments

Conversation

@loadinglucian

@loadinglucian loadinglucian commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

The provisioner hardcoded php-autorelease-publish while docs/repository-settings.md documents both php-autorelease-publish and php-autorelease-canary. Re-provisioning from scratch would have recreated the missing canary environment. Environments are now named at the call site.

Summary by CodeRabbit

  • New Features

    • Added a required, repeatable option for configuring multiple deployment environments.
    • Environment protection and administrator bypass validation now apply to each specified environment.
    • Environment names are handled safely, including names containing special characters.
    • Success messages now list all configured environments.
  • Documentation

    • Updated repository configuration guidance to include the publish and canary environments.

@cursor

cursor Bot commented Aug 2, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_365cb69d-0ad5-40a7-8359-76b2d7c1deb6)

@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b57a8b9c-039d-4b3e-ac0e-0d752f45b843

📥 Commits

Reviewing files that changed from the base of the PR and between ca87f51 and a78e5b8.

📒 Files selected for processing (1)
  • scripts/configure-github-autorelease
🚧 Files skipped from review as they are similar to previous changes (1)
  • scripts/configure-github-autorelease

📝 Walkthrough

Walkthrough

The autorelease configuration command now accepts repeatable environment names. It URL-encodes each name for GitHub API paths, applies protection settings, and validates administrator bypass per environment. The repository settings documentation includes both autorelease environments.

Changes

Autorelease environment configuration

Layer / File(s) Summary
Configure protected environments
scripts/configure-github-autorelease, docs/repository-settings.md
The command requires repeatable --environment NAME options, configures each supplied environment, validates administrator bypass per environment, reports the configured names, and safely encodes environment names in API paths. The documentation shows both autorelease environment arguments.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the change but omits the required Verification and Security and licensing sections. Add the Verification and Security and licensing sections, and complete the required checklist items.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes provisioning all documented autorelease environments.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/provision-documented-environments

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/configure-github-autorelease`:
- Around line 129-134: URL-encode each environment name in the API path within
the environment loop, using quote(environment_name, safe="") before constructing
the repos/{args.repo}/environments/{...} endpoint. Preserve the existing API
call behavior while ensuring names containing slashes remain a single path
segment.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 185a3432-c235-4371-be84-4179a086230d

📥 Commits

Reviewing files that changed from the base of the PR and between e863e8f and ca87f51.

📒 Files selected for processing (2)
  • docs/repository-settings.md
  • scripts/configure-github-autorelease

Comment thread scripts/configure-github-autorelease
@cursor

cursor Bot commented Aug 2, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_f7791590-a9a9-4de3-b8b9-57ffe69deebf)

@loadinglucian
loadinglucian merged commit e439d65 into main Aug 2, 2026
5 of 6 checks passed
@loadinglucian
loadinglucian deleted the fix/provision-documented-environments branch August 2, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant