On 10/13/22 3:26 AM, Michael Bien wrote:
When you clone a repo, gh won't have any actions enabled (I just checked
to confirm that it is still the case). The action tab will show a
confirmation/warning:
"Workflows aren’t being run on this forked repository"
I just checked to confirm, too, and I see the same thing. The confusing
part is that it still shows "Allow all actions and reusable workflows"
as selected under Settings > Actions > General > Actions permissions,
but it seems those settings are ignored until workflows are enabled on
the Actions tab.
Well, the other confusing part is that I do not recall ever clicking the
green button that says:
"I understand my workflows, go ahead and enable them"
on my old NetBeans fork. Maybe GitHub changed it, or maybe I forgot.
My main concern was that I might be triggering builds against Apache's
limit (2,000 minutes/month?). Now I understand they run against my
account on non-pull-request branches, and only against Apache's account
when the branch is associated with a pull request.
It's hard to find that information in the GitHub Help pages. The best I
can find is:
https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions
About spending limits
"GitHub charges usage to the account that owns the repository where a
workflow is run."
Thank you for helping me understand all this better!
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
