On 15/08/2023 20:01, Junio C Hamano wrote:
See [1], where main currently is at v2.41.0.
[1] https://github.com/git/git/tree/main
Ah, that one. The CI job is unfortunately attached to that tree and
updating 'master' and 'main' with the same commit at the same time
wastes CI cycles, so I had to tentatively stop updating it.
It used to be that 'main' was set to lag behind 'master' by 24 hours
or so to prevent the problem---CI notices that the commit updated
'main' has been already dealt with 24 hours ago at 'master' and
refrains from wasting time on it. But resurrecting it would still
make folks confused about how 'main' is different from 'master'.
Perhaps it is a good time to remove stale 'main' and keep only
'master' there?
An alternative might be to exclude one of the branches in the workflow
file, as per [1].
Andy
[1]
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-excluding-branches
