Stop building previous commit if new pushed by default

[nilay994]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Dear GitHub devs,

I think all CI/CD pipelines can have previous commit builds forfeited if a newer commit is pushed. There is an option to do so, but it is not default. Which means most part of the world is still occupying servers for old commits. Default behaviour of forfeiting hopefully saves a lot of compute & for teams which really need old commit build results can enable some option.

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

[maheerCodes]

hey Nilay 👋 .
agree this would save a ton of wasted compute across the platform ,,,especially for repos with frequent pushes /force-pushes during active dev

in the meantime,for anyone reading this who wants it now,,, its a one-time opt-in per workflow rather than something you have to remember to add manually each run :

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

add that near the top of your workflow yaml(same level as on: and jobs:)and any in-progress run for the same branch gets cancelled automatically the moment a new commit is pushed.set it once per workflow file and youre done ,,, no per-push action needed.

on the actual feature request ,,, id guess the reason its opt-in rather than default is that some teams genuinely want every commit built(e.g. for audit trails ,bisecting regressions ,or release branches where every commit needs a clean build record),,so making it default could break those workflows silently. a middle ground might be defaulting it on for non-protected branches only (feature branches ,PRs)while leaving protected / release branches as build-everything by default

still,,,,,,,worth the feedback. even an opt-in-by-default-for-new-repos toggle in org settings would help adoption a lot 💙💙