Skip to content

Commit

Permalink
chore: test external push to protected branch
Browse files Browse the repository at this point in the history
Pushing this commit to the `libevm` branch fails (by design) because of branch protection requiring a PR. I want to test what happens if, once the PR is approved and all status checks pass, I _locally_ `git merge --ff-only` on the `libevm` branch before pushing to GitHub. Will it recognise and honour the PR?

Without this, the GitHub PR merge uses `--no-ff`, which isn't always desirable.
  • Loading branch information
ARR4N committed Oct 10, 2024
1 parent 77c5571 commit 18d6153
Showing 0 changed files with 0 additions and 0 deletions.

0 comments on commit 18d6153

Please sign in to comment.