Sjors Provoost 576828e732 ci: test-each-commit merge base optional ... The ci "test-each-commit" job fetches the PR branch being tested with a depth of (# of commits in PR + 2), and then tries to run tests on commits after the most recent merge commit. When a PR is opened against a bitcoin core branch, a merge commit is always guaranteed to exist within the fetch depth, because bitcoin core branches always point at merge commits. However, in fork repositories, pull requests can be opened based on other branches that don't contain recent merge commits, and this will currently cause git rev-list to fail with fatal: bad revision '^^@'. Work around this problem by not requiring a recent merge commit, and just testing on all fetched commits if a merge commit can't be found. Co-authored-by: Ryan Ofsky <ryan@ofsky.org>		2024-06-25 20:03:44 +02:00
..
ISSUE_TEMPLATE	doc: Fill in the required skills in the good_first_issue template	2023-08-30 14:02:08 +02:00
workflows	ci: test-each-commit merge base optional	2024-06-25 20:03:44 +02:00
PULL_REQUEST_TEMPLATE.md	doc: Add redirect for GUI issues and pull requests	2020-06-08 10:06:02 -04:00