Thread (1 message) 1 message, 1 author, 2020-05-05

Re: [PATCH v3 3/3] fixup! CI: limit GitHub Actions to designated branches

From: Junio C Hamano <hidden>
Date: 2020-05-05 18:59:22

Đoàn Trần Công Danh  [off-list ref] writes:
Should we want to enable GitHub Action for all repo-s, except git/git
and gitster/git. We'll want to have this patch fix-up to the previous
one.
Just to get everybody on the same page,

	git/git has only the primary integration branches and tags
	gitster/git has broken out individual topics

We do want to build everything in git/git repository.

I do not have Actions enabled for gitster/git repository.

I expect general contributors to fork from the former, push their
work on their own branches (not the copies of the public integration
branches like 'master', 'next', etc.) so that they can throw a pull
request at git/git.
 jobs:
   windows-build:
+    if: >-
+      ${{
+      (github.repository_owner != 'git' && github.repository_owner != 'gitster') ||
+      github.ref == 'refs/heads/maint' ||
+      github.ref == 'refs/heads/master' ||
+      github.ref == 'refs/heads/next' ||
+      github.ref == 'refs/heads/jch' ||
+      github.ref == 'refs/heads/pu'
+      }}
Ialready asked not to make this about me.  You do not want to search
and replace 'gitster' with 'peff' or 'dscho' or whatever string,
only because/when I chose to retire.  Such an occasion shouldn't be
a significant event to the project's codebase.

Thanks.

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help