On 29.01.23 03:16, John Neffenger wrote:
On 1/28/23 10:55 AM, Łukasz Bownik wrote:
I noticed that as soon as I push a branch to my copy of the
repository CI
picks it up. Is there a way to postpone CI process until a PR is being
created?
Can't we just disable GitHub Actions in the forked repository?
I did that under Settings > Code and automation > Actions > General,
where I selected "Disable actions" under "Actions permissions."
yes of course! I read the question wrong since I tried to find a way how
to configure workflows started by PRs while reading this (apache
projects don't have the settings menu).
Actions are usually disabled on fresh clones. I believe github asks
first before enabling them if I remember correctly. Since they would run
on your account, not on the account of the origin repo.
sorry for causing confusion - everything what runs on your clone can be
configured from your settings,
-mbien
I disabled the actions so that I could sync the upstream branches with
my fork and push the changes to 'master' and my feature branches
without triggering any tests.
Is that an okay thing to do?
John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
