Replies: 2 comments 1 reply
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Hi! I can confirm what you're seeing: steps inside a composite action always run sequentially, one after another. The parallel-steps capability from the June 2026 changelog applies to steps defined directly in a workflow job, not to the steps inside a composite action. That's also consistent with this thread being labeled "In Backlog" — the team is aware, but it isn't supported yet. A workaround that works today: split your composite action into smaller composite actions (one per dependency source) and call them from separate jobs in the calling workflow. Jobs in the same workflow run in parallel on separate runners by default: jobs:
install-npm-deps:
runs-on: ubuntu-latest
steps:
- uses: your-org/setup-deps/npm@v1
install-pip-deps:
runs-on: ubuntu-latest
steps:
- uses: your-org/setup-deps/pip@v1
build:
needs: [install-npm-deps, install-pip-deps]
runs-on: ubuntu-latest
steps:
- run: ./build.shThis gets you the same benefit — the two install jobs overlap in time — with a small amount of extra YAML. The Hope that helps as a stopgap until composite actions support parallel steps natively! |
|
@MrAbdulSamadDEV, thanks for participating in GitHub Discussions! Please note: we’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team. You can read our updated Code of Conduct and the announcement for more details. Please feel encouraged to continue engaging in Discussions as your authentic self though. We appreciate you being a part of the Community 🌟 We recommend you validate any output a generative AI tool uses and retain your original voice. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
I saw this on my RSS reader: https://github.blog/changelog/2026-06-25-actions-steps-can-now-be-run-in-parallel/ and thats SO COOL! Thanks for shipping this!
... by the way, it seems it didn't work in a composite actions.
I'm using composite actions to install dependencies from multiple sources (which should get benefit of parallel steps i guess), so It would be nice if we can use them in a composite actions!
Yes I tried but didn't work
Workflow: https://github.com/cinderella-project/iMast/blob/8586e61e10ed06e68b9d55a6e1c86a35d4faed22/.github/actions/prepare/action.yml
Failed https://github.com/cinderella-project/iMast/actions/runs/28202201210/job/83544324588 , log:
All reactions