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

Auto-merge bot PRs #47

Merged
merged 1 commit into from
Apr 4, 2022
Merged

Auto-merge bot PRs #47

merged 1 commit into from
Apr 4, 2022

Conversation

fg-j
Copy link

@fg-j fg-j commented Apr 4, 2022

Summary

🚨 Auto-merging will need to be enabled on this repository before this PR merges 🚨
When PRs are made by bots, approve them if they are passing tests and set them to auto-merge once all checks pass.

Use Cases

Checklist

  • I have viewed, signed, and submitted the Contributor License Agreement.
  • I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
  • I have added an integration test, if necessary.
  • I have reviewed the styleguide for guidance on my code quality.
  • I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@fg-j fg-j requested a review from a team as a code owner April 4, 2022 15:12
@fg-j fg-j requested review from ryanmoran and sophiewigmore April 4, 2022 15:12
@fg-j fg-j added the semver:patch A change requiring a patch version bump label Apr 4, 2022
@sophiewigmore
Copy link
Member

It looks like auto-merging has been enabled in settings already.

@sophiewigmore sophiewigmore merged commit 38e0997 into main Apr 4, 2022
@sophiewigmore sophiewigmore deleted the auto-merge branch April 4, 2022 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch A change requiring a patch version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants