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

add PR merge action #296

Merged
merged 1 commit into from
Apr 2, 2020
Merged

add PR merge action #296

merged 1 commit into from
Apr 2, 2020

Conversation

brodycj
Copy link
Owner

@brodycj brodycj commented Apr 2, 2020

https://github.com/marketplace/actions/pull-request-merge-command

to pull & test from master before merging a PR

General motivation:

  • It is safest to pull and test from master before merging a PR GitHub should test this automatically, doesn't hurt to pull from master before merging though.
  • There are PRs such as CLI command func logging snapshot with example #277 which I may want to keep testing from the GitHub UI before I am finally ready to merge.

I did test this action on my own scratch project, hope it will work as expected on this one.

@brodycj brodycj self-assigned this Apr 2, 2020
@brodycj brodycj merged commit 9712d41 into master Apr 2, 2020
@brodycj brodycj deleted the brodybits-pr-merge-action branch April 2, 2020 00:35
brodycj added a commit that referenced this pull request Apr 8, 2020
brodycj added a commit that referenced this pull request Apr 8, 2020
This reverts commit 9712d41.

Rationale: I do not have a very good feeling that this
GitHub action works 100% correctly and securely.

For future reconsideration.
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