Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(automerge): don't reassign failing PRs if assignAutomerge=true #14065

Merged
merged 1 commit into from Feb 7, 2022

Conversation

rarkins
Copy link
Collaborator

@rarkins rarkins commented Feb 7, 2022

Changes:

Skips reassigning a PR with failing commits if config.assignAutomerge=true (because they already would have been assigned anyway).

Context:

Partly solves #4624

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 31.68.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@@ -358,6 +358,7 @@ export async function ensurePr(
!existingPr.hasAssignees &&
!existingPr.hasReviewers &&
config.automerge &&
!config.assignAutomerge &&
Copy link
Member

Choose a reason for hiding this comment

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

Don't work for automerge branch? 🤔

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Edge of an edge case, good catch :)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants