-
Notifications
You must be signed in to change notification settings - Fork 180
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
feat(rulesets): initial support repository rulesets (semi-dark release with the potential for breaking changes) #1029
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
> [!WARNING] | ||
> Support for Repository Rulesets is still under development. | ||
> Details may still change, like how the configuration is defined in the `settings.yml`. | ||
> Please follow [#732](https://github.com/repository-settings/app/issues/732) for progress updates. | ||
> Feedback is appreciated, but adopt cautiously, with the expectation of breaking changes until support is fully released. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while this should be fully functional with the current schema, it mirrors the github API expectations, which are somewhat cryptic for a non-programatic context. we prefer to mirror the github API most of the time, but i'm leaning away from that in this case
because of that, i want to release this progress in a semi-dark pre-release fashion. this warning is included in the docs to attempt to make that visible
🎉 This PR is included in version 4.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
while still WIP for ergonomics, this is production ready, but with the potential for breaking changes before considered ready for full release. my plan is to release it semi-dark so that it can be used, but without highlighting it beyond the release notes or the specific docs page (which warns about the potential for breakages)
for #732