-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using GitHub Actions #373
Comments
@sidvishnoi can probably guide us here. He's done some gh actions before. |
@saschanaz is correct. Someone who's member of W3C need to join the public beta and enable GitHub Actions. |
Ok, so no of us have enough power? @siusin maybe can help us? |
Just to be clear, do they need need to be enabled at the org level? |
@marcoscaceres Probably yes, as I didn't see anything about enabling for each repo. |
Hi all, I've already informed our sys-team about this request. If there is no objection from them, I'll enable GitHub Actions on Friday. Apologise for the delay. |
Thanks so much @siusin! That's great! |
Still in the queue for the beta... will try to enable GitHub Actions once I gain access :) |
Closed by #386 🎉 |
@marcoscaceres I tried adding NPM actions via this page but it says we are not ready:
Maybe an W3C member should explicitly join the public beta of GitHub Actions, so could you join from https://github.com/features/actions?
The text was updated successfully, but these errors were encountered: