-
Notifications
You must be signed in to change notification settings - Fork 3
Have a philosophy for replacing vs. merging vs. do-nothing #42
Copy link
Copy link
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation
Milestone
Description
When adding configuration (e.g. ruff rules, pre-commit hooks, CI config, etc.) if there is existing config, it is not obvious how to interact with it. Should we replace it? (probably hardly ever!) Should we merge it together with the default in some way? (Tricky, but good for updating to latest best practice.) Should we just give up and leave the config alone (very easy, potentially missed opportunities.)
Some thought needs to go into this, and its ramifications need to be reckoned for the three examples mentioned above.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation