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
I have a workflow that checks out the current repository's default branch and pushes a commit to it. A second job called by the workflow checks out the repository again. I'm finding that the second job checks out the same commit as the first job (e.g. both check out commit A), even though the first job commits and pushes commit B to the branch, so I intended and expected the second job to check out commit B.
I am seeing the same problem.
I have a workflow with 2 jobs, JobA & JobB. I commit and push changes to the branch on JobA, in JobB when checkout@V3 runs i get the latest commit on JobA before i pushed the commit
After investigation into how this action works, I believe DawnbrandBots/yaml-yugi-ko@2d3e1ae is the correct approach when we push within a workflow run, because by default, it checks out the triggering SHA (ish) rather than the branch.
MaximePouce
added a commit
to Infomaniak/desktop-kDrive
that referenced
this issue
May 22, 2024
I have a workflow that checks out the current repository's default branch and pushes a commit to it. A second job called by the workflow checks out the repository again. I'm finding that the second job checks out the same commit as the first job (e.g. both check out commit A), even though the first job commits and pushes commit B to the branch, so I intended and expected the second job to check out commit B.
Example run:
Possibly related to #1036
The text was updated successfully, but these errors were encountered: