Skip to content

Remove pull request guard#2475

Draft
samchungy wants to merge 6 commits into
mainfrom
remove-pr-guard
Draft

Remove pull request guard#2475
samchungy wants to merge 6 commits into
mainfrom
remove-pr-guard

Conversation

@samchungy

@samchungy samchungy commented Jun 18, 2026

Copy link
Copy Markdown
Member

This existed before Aaron's fix Renovate to recognise buildagencytoken as a bot

@changeset-bot

changeset-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 95eb353

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
skuba Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@samchungy
samchungy marked this pull request as ready for review June 19, 2026 06:45
@samchungy
samchungy requested a review from a team as a code owner June 19, 2026 06:45

skuba previously skipped pushing autofixes on Renovate branches when no open pull request was associated with the current commit, as this would interfere with Renovate's pull request creation

If you notice any issues with skuba Renovate branches stuck in an edited or blocked state, please reach out in #skuba-support.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

How would teams notice this? Would the branches be visibly stuck in the Dependency Dashboard without an option to force-raise the PR?

Is there something check we could run against the gh CLI in e.g. 60 days to see if there is an increase in stale Renovate branches across the org?

Comment on lines +5 to +9
lint: Remove Renovate pull request guard from autofix

skuba previously skipped pushing autofixes on Renovate branches when no open pull request was associated with the current commit, as this would interfere with Renovate's pull request creation

If you notice any issues with skuba Renovate branches stuck in an edited or blocked state, please reach out in #skuba-support.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
lint: Remove Renovate pull request guard from autofix
skuba previously skipped pushing autofixes on Renovate branches when no open pull request was associated with the current commit, as this would interfere with Renovate's pull request creation
If you notice any issues with skuba Renovate branches stuck in an edited or blocked state, please reach out in #skuba-support.
lint: Push autofixes on Renovate branches without an open pull request
A race condition can occur when skuba is ready to push [GitHub autofixes](https://seek-oss.github.io/skuba/docs/deep-dives/github.html#github-autofixes) to a Renovate branch before the bot opens a corresponding pull request. skuba previously skipped the push operation in this scenario, which ensured Renovate would reliably proceed to pull request creation but required human intervention to subsequently apply fixes to the branch. Recent improvements to the [`gitIgnoredAuthors`](https://docs.renovatebot.com/configuration-options/#gitignoredauthors) configuration option in Renovate should allow skuba to safely push autofixes ahead of pull request creation.
[Reach out](https://github.com/seek-oss/skuba/blob/main/CONTRIBUTING.md#i-want-to-discuss-or-report-something) if you notice your Renovate branches are getting stuck in an edited or blocked state.

@samchungy
samchungy marked this pull request as draft July 15, 2026 13:07
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.

3 participants