Add githook script to alert on changes that require re-installs #6757
Conversation
|
Would love some input on how to best check for provider/plugin changes. Ideally a minimal set that most likely requires at least a new |
|
The vast majority of entrypoints are registered in the |
|
@alexrashed what's your take on it, should we continue here or just close if for now? Haven't seen any push in that direction so I'd say it's not super urgent |
|
That's hard to say. I think the entrypoints still cause some confusion, but if we want to solve it, we should make sure that the solution catches all these issues (in order to avoid even more confusion).
|
Uses pre-commit to register a local python script that will be executed after running
git checkout, i.e. when switching branches. It contains a list of files and if the diff between the two commits includes a change in these files, it will output a warning.How to use:
Run
make init-githooksto set up the hooks for your current repository.You can trigger the behavior by switching to any branch with some change in any of the files that are listed in the script.
Some things that I think should still be included before an initial merge:
References: