You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
actions/checkout seems to get a commit when triggered, not the latest one when you run the same workflow with the concurrency settings.
Let's say we have an example that pushes a commit when triggered, like:
concurrency: ${{ github.workflow }} # set the concurrency setting at workflow level# ...
- uses: actions/checkout@v3
- run: | # making some file and git config changes git commit -am "update something" git push
If we run this workflow twice immediately, the second run won't have a commit pushed on the first run. Is there a way to get it on the second?
This can be resolved by git pull'ing before committing but I wonder if actions/checkout could resolve it somehow, and I guess it'd be a better way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
actions/checkout
seems to get a commit when triggered, not the latest one when you run the same workflow with the concurrency settings.Let's say we have an example that pushes a commit when triggered, like:
If we run this workflow twice immediately, the second run won't have a commit pushed on the first run. Is there a way to get it on the second?
This can be resolved by
git pull
'ing before committing but I wonder ifactions/checkout
could resolve it somehow, and I guess it'd be a better way.Beta Was this translation helpful? Give feedback.
All reactions