git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] ci: cancel stale pull request workflow runs

From
Harald Nordgren <haraldnordgren@gmail.com>
Date
Aug 31, 2026, 11:12 UTC
Message-ID
<CAHwyqnV5YTJsAnDDHQj0gwmoWXEgnPSJ8tJCcXrg12vBvtwFfA@mail.gmail.com>
In-Reply-To
<xmqqqzjfz0ba.fsf@gitster.g>
Show 17 quoted lines
> If a user has CI enabled on their own repository, pushes a commit
> there, and opens a pull request, wouldn't GitHub Actions trigger
> two events for the same commit at the tip of the pushed branch?
>
> Before this change, both events are assigned to the same concurrency
> group (the commit object name).  One waits while the other runs, and
> the skip-if-redundant logic stops the second one early without
> wasting cycles on the same commit.  With this change, the
> concurrency groups for these two events are separate.  Would we end
> up building and testing the same commit twice in parallel?
>
> I suspect this may not be a problem in practice given how our
> contributors use GitHub Actions in our official repositories (either
> those owned by gitgitgadget or git).  They push to their own
> repositories where CI may not be enabled, so 'push' does not
> trigger.  Still, I thought it better to bring this up before the
> change gets merged and wastes build cycles.
Concurrency groups don't span repos, so I don't see a solution to that.
Harald
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 8 in “ci: cancel stale pull request workflow runs”
  1. ci: cancel stale pull request workflow runsHarald Nordgren via GitGitGadget, Jul 31, 2026
  2. Harald NordgrenAug 21, 2026
  3. Junio C HamanoAug 26, 2026
  4. ci: cancel stale pull request workflow runsHarald Nordgren via GitGitGadget, Aug 30, 2026
  5. Junio C HamanoAug 30, 2026
  6. Harald NordgrenAug 31, 2026
  7. Junio C HamanoAug 31, 2026
  8. ci: cancel stale pull request workflow runsHarald Nordgren via GitGitGadget, Aug 31, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.