Skip to content

Allow repos to enable effects on pull requests and additional branches#581

Merged
Mic92 merged 1 commit intomainfrom
effects-config
Feb 25, 2026
Merged

Allow repos to enable effects on pull requests and additional branches#581
Mic92 merged 1 commit intomainfrom
effects-config

Conversation

@Mic92
Copy link
Member

@Mic92 Mic92 commented Feb 25, 2026

No description provided.

@Mic92 Mic92 force-pushed the effects-config branch 3 times, most recently from d458c18 to b5aa5d5 Compare February 25, 2026 13:53
Effects are useful for deployment and other impure CI steps, but until
now they were restricted to the default branch. Some workflows need
effects on pull requests (e.g. preview deployments) or on additional
branches like staging or release branches.

Add two new settings to the per-repo buildbot-nix.toml:
effects_on_pull_requests (bool) and effects_branches (list of glob
patterns). Both default to off, preserving existing behavior.

To prevent a malicious PR from granting itself effects access, these
settings are always read from origin/<default_branch> via git show,
never from the PR worktree. For PR builds, GitLocalPrMerge now fetches
the default branch ref alongside the PR SHAs so the ref stays current.

Also fix get_project_url() dropping the port from the Gitea instance
URL (url.hostname strips port), causing git clone to fail when Gitea
runs on a non-standard port.
@Mic92 Mic92 added this pull request to the merge queue Feb 25, 2026
Merged via the queue into main with commit 608f80f Feb 25, 2026
3 checks passed
@Mic92 Mic92 deleted the effects-config branch February 25, 2026 15:13
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