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
..
ci.yml	Meta: Update for GitHub org rename to LadybirdBrowser	2024-06-09 13:02:56 +02:00
dev-container.yml	CI: Use ladybirdbrowser namespace for devcontainer	2024-06-22 11:10:15 -04:00
ladybird-js-artifacts.yml	CMake: Add ENABLE_GUI_TARGETS option to enable disabling GUI components	2024-07-07 09:51:29 -06:00
lagom-template.yml	Ladybird/AppKit: Port TaskManager window to Swift	2024-07-21 15:55:47 -06:00
libjs-test262.yml	CI: Install nasm on the test262 runner	2024-07-09 20:08:38 -04:00
lint-code.yml	CI: Restore the code linting job	2024-06-16 15:30:28 -04:00
lint-commits.yml	CI: Restore the code linting job	2024-06-16 15:30:28 -04:00
nightly-android.yml	CI: Fixed the broken steps in nightly-android	2024-07-11 23:26:05 -06:00
notes-push.yml	CI: Make notes-push workflow return zero even when “git push” fails	2024-07-23 11:47:55 +02:00