Slow job setup with composite actions self-repository syntax

[tstellar]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Actions Checkout

Discussion Details

I've noticed that every since switching to the new self-repository syntax for composite actions that the "Setup Job" step is taking several minutes to complete. We have a very large repository which does take a while to clone, but I'm wondering if this can be optimized some how. For example:

https://github.com/llvm/llvm-project/actions/runs/32781791698/job/97606726563

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[tomm1990]

looking at that job, Setup Job isn’t “mysteriously slow”. almost all of it is:

Download action repository 'llvm/llvm-project@b10b3f59…' (~2m50s of the ~2m52s Setup Job)

that lines up with $/.github/workflows/get-llvm-version (and friends) resolving same-repo actions at the running commit without a prior checkout - for llvm-project that means the runner pulls the monorepo as an action package up front. sparse-checkout inside the composite can’t shrink that download.

before I push a workaround though - a couple things:

1. on the prepare job you call $/.github/workflows/get-llvm-version before any checkout (the composite does its own sparse checkout). was that the reason you moved off ./ - i.e. you need the action without checking out first?
2. have you already timed Setup Job with ./.github/workflows/get-llvm-version after a sparse actions/checkout of just the action paths, or is that still untested on your side?
3. is the ask here mainly “please make $/ not fetch the whole tree” (product), or do you want a same-repo pattern that avoids the monorepo download today?