mirror of
https://github.com/ArduPilot/ardupilot.git
synced 2026-10-06 19:00:27 +08:00
James HarveyandClaude Opus 5
20fe331ef4
The release procedure pushes about twenty tags at a single commit: the per-vehicle -stable and -beta tags and the numbered ones such as Copter-4.7.1. Only pre-commit.yml's push trigger carries a branch filter, so every other workflow runs for each of those tag pushes, and path filters are not evaluated for tag pushes, so the paths-ignore lists do not thin them out. The 4.7.1 release produced 438 push-event runs for one commit; 18 came from the ArduPilot-4.7 branch push and the other 420 from the tags, each re-running the same jobs on the same commit. 4.7.0 produced 437, and the pattern goes back to at least 4.6.2. Filter push triggers to branches. '**' matches every branch, so branch pushes behave exactly as before; tag pushes stop triggering workflows. The tags still show the commit's checks, since check results attach to the commit; those are the release-branch push's runs, trimmed by the usual path filters as on any other branch. test_scripts.yml used the list form of 'on', which cannot carry a filter, so it is expanded to the mapping form. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>