sideshowbarker 1d03944a9c CI: Make notes-push workflow return zero even when “git push” fails ... It’s possible but unlikely that a push of generated notes back to the remote can fail with a message like > [remote rejected] ... cannot > lock ref 'refs/notes/commits': is at > f3648f50bb but expected 47686bf473 See https://github.com/LadybirdBrowser/ladybird/actions/runs/10054314539 So this change makes the call to “git push” for notes not return 0 even if it fails — because it’s not actually a fatal error when it happens, and not something we need to stop and fix. Instead, it fixes itself. Specifically: If one CI job for a PR merge/push to master generates some notes but fails to push them to the origin, the notes don’t get dropped on the floor and lost. Instead, the notes-generator tool looks at the entire history; and if it finds commits that don’t have notes — even if those commits are not part of the PR push/merge it’s operating on — it generates notes for those. In other words, if notes for one PR push/job fail for some reason to get pushed back to the remote, they get regenerated by the next PR push/job.		2024-07-23 11:47:55 +02:00
..
actions	CI: Remove a couple unneeded system dependencies	2024-07-23 08:59:05 +02:00
workflows	CI: Make notes-push workflow return zero even when “git push” fails	2024-07-23 11:47:55 +02:00
CODEOWNERS	Meta: Remove myself from CODEOWNERS	2024-06-29 20:26:20 -06:00
dependabot.yml	Meta: Add dependabot configuration to update github actions	2023-01-16 20:59:23 -08:00
FUNDING.yml	Meta: Add Donorbox link in FUNDING.yml	2024-07-10 08:12:39 +02:00
stale.yml	Meta: Instruct stale-bot to ignore pr-is-blocked PRs	2022-10-15 12:05:57 +02:00