Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Description
Suggestion
OurConfigurations andMaintenance > Versioning docs specify that changes to the recommended configs need to be marked as a breaking change. But nothing I can spot enforces that changes torecommended.ts or its friends be labeled asbreaking change.
To help prevent slipups in the future, let's add some kind of automation that marks PRs as failing if they do touch a recommended config file and don't have thebreaking change label.