Git's maintainer usually don't have enough time to debug the failure of invidual feature branch, they usually want to look at intergration branches only. Contributors now can have GitHub Actions as an opt-in option, should they want to check their code, they will push into designated branch. Signed-off-by: Đoàn Trần Công Danh <congdanhqx@xxxxxxxxx> --- .github/workflows/main.yml | 14 +++++++++++++- Documentation/SubmittingPatches | 3 ++- 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index fd4df939b5..9bba0ce068 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -1,6 +1,18 @@ name: CI/PR -on: [push, pull_request] +on: + pull_request: + push: + branches: + - maint + - master + - next + - jch + - pu + - 'for-ci**' + tags: + - '**' + - '!**wip**' env: DEVELOPER: 1 diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 8686318550..e516b080df 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -79,7 +79,8 @@ test your changes on Linux, Mac (and hopefully soon Windows). See GitHub-Travis CI hints section for details. Alternately, you can use GitHub Actions (which supports testing your changes -on Linux, macOS, and Windows) by pushing into a branch in your fork +on Linux, macOS, and Windows) by pushing into a branch whose name starts +with "for-ci", or a tag whose name doesn't have `wip`, or opening a GitHub's Pull Request against https://github.com/git/git.git or a fork of that repository. -- 2.26.2.672.g232c24e857
