Update the automation to bump erlang/elixir patches in CI (backport #7991) #7996
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
so that the workflow fails if the branch already exists, instead of just skipping We had a period of many weeks where the elixir workflow was being skipped because the branch was left around after a PR was closed, so we want to avoid that in the future (cherry picked from commit bb6c503) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml
mergify bot
added a commit
that referenced
this pull request
Apr 26, 2023
…7991) (#7996) * Update the automation to bump erlang/elixir patches in CI so that the workflow fails if the branch already exists, instead of just skipping We had a period of many weeks where the elixir workflow was being skipped because the branch was left around after a PR was closed, so we want to avoid that in the future (cherry picked from commit bb6c503) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml * Fixup backport --------- Co-authored-by: Rin Kuryloski <kuryloskip@vmware.com> (cherry picked from commit d59a1db) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml
HoloRin
added a commit
that referenced
this pull request
Apr 26, 2023
…7991) (backport #7996) (#7997) * Update the automation to bump erlang/elixir patches in CI (backport #7991) (#7996) * Update the automation to bump erlang/elixir patches in CI so that the workflow fails if the branch already exists, instead of just skipping We had a period of many weeks where the elixir workflow was being skipped because the branch was left around after a PR was closed, so we want to avoid that in the future (cherry picked from commit bb6c503) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml * Fixup backport --------- Co-authored-by: Rin Kuryloski <kuryloskip@vmware.com> (cherry picked from commit d59a1db) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml * Fixup backport --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Rin Kuryloski <kuryloskip@vmware.com>
mergify bot
added a commit
that referenced
this pull request
Apr 26, 2023
…7991) (backport #7996) (#7997) * Update the automation to bump erlang/elixir patches in CI (backport #7991) (#7996) * Update the automation to bump erlang/elixir patches in CI so that the workflow fails if the branch already exists, instead of just skipping We had a period of many weeks where the elixir workflow was being skipped because the branch was left around after a PR was closed, so we want to avoid that in the future (cherry picked from commit bb6c503) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml * Fixup backport --------- Co-authored-by: Rin Kuryloski <kuryloskip@vmware.com> (cherry picked from commit d59a1db) # Conflicts: # .github/workflows/update-elixir-patches.yaml # .github/workflows/update-otp-patches.yaml * Fixup backport --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Rin Kuryloski <kuryloskip@vmware.com> (cherry picked from commit 3df9db0) # Conflicts: # .github/workflows/update-elixir-patches.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #7991 done by Mergify.
Cherry-pick of bb6c503 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com