ci: commitish must point to the name of the branch or tag that triggered the workflow run
#14
Conversation
This file contains 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
juanjjaramillo
force-pushed
the
juanjjaramillo/revert_change
branch
from
996bbb3
to
5cbc302
Compare
…d the workflow run This reverts commit 8de525f.
juanjjaramillo
force-pushed
the
juanjjaramillo/revert_change
branch
from
5cbc302
to
14e7717
Compare
juanjjaramillo
changed the title
commitish must point to the name of the branch or tag that triggered the workflow run
juanjjaramillo
added
Release/fix
alankritdabral
added a commit
to alankritdabral/testbed
that referenced
this pull request
Jan 2, 2024
…hat triggered the workflow run (juanjjaramillo#14)" This reverts commit d147229.
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.
Description
This is a long story. It all started when this error appeared. The suggested solution by one of the developers works, but another developer argues it will not work when working with different branches for more elaborate scenarios.
I decided to follow the advice of the developer that makes a better case.
Checklist
Mandatory:
If applicable: