Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi all,
I have the following setup which is working fine (i.e. it's doing the
git push
):W1
is fired on branchA
, checks out branchA
, and uploads some artifacts.W2
is fired on branchA
, waits forW1
to finish, checks out branchB
, then downloads the artifacts, copies them to the workspace, and does thegit push
to branchB
.Example of successful run: W1 and W2.
Now, I've tried to modify it to use only one workflow with two jobs, but then the
git push
is telling me there is nothing to push:W
is fired on branchA
, and it contains two jobs,J1
, andJ2
.J1
checks out branchA
, and uploads some artifacts.J2
waits forW1
to finish, checks out branchB
, then downloads the artifacts, copies them to the workspace, and does thegit push
to branchB
.Examples of failed run: this or this other.
It seems like, with the second approach, GitHub still thinks I'm working on a branch
A
checkout. Is this correct? Can this still be done in a single workflow?Thanks,
Roberto.
Beta Was this translation helpful? Give feedback.
All reactions