-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[FEAT]: Add support for required_workflows APIs #1475
Comments
Is anyone working on this already? |
@aitorpazos please feel free to open up a PR if you'd like! To the best of my knowledge nobody is working on it at the moment. You can find our CONTRIBUTING.md here. |
Happy to pick this up if no one is working on it. Will need to wait for the next go-github release (to pick up this bug fix), but then I can get started if no one objects. |
Hi @sam-robson , do you have any news on this? Thanks! |
Hey @philippeboyd, I have a PR ready to go, but I am still waiting for the next go-github release |
Ran into a significant bump here - it looks as if GitHub are in the process of scrapping Required Workflows, see this comment on the PR for more details. |
I've received a response to my support ticket, for those interested: "Required workflows are being brought back from public to private beta. Organizations that are already utilising required workflows will still be able to access them however no new organisations will be signed up to the beta. Required workflows are being moved into the new Repository Rules - currently in Public Beta. The workflow functionality is not available at this stage, however it is expected to be before the planned date for Repository Rules to be generally available around July 31st." |
👋 Hey Friends, this issue has been automatically marked as |
Describe the need
Required workflows is a really cool new feature that should be supported via terraform.
https://docs.github.com/en/rest/actions/required-workflows?apiVersion=2022-11-28#create-a-required-workflow
SDK Version
No response
API Version
2022-11-28
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: