Here I'll go freestyle proposing a raw and naive solution to automatically open an issue every time a new hook is added to the core.
Issue will point missing hooks in the available hooks table.
We could exploit a GitHub action to run a python script when pushing in the doc.
The script should scan the existing functions in this module and the modules in this folder.
Detected functions can be stored in a JSON or something (e.g. a JSON with a key new_hooks, where new hooks are stored each time).
If the already stored differ from the detected ones (i.e. a new hook exists), we set an environment variable to be used in a further step of the action.
If the env. variable is true, we open an issue with the hooks in the new_hooks key.
Here I'll go freestyle proposing a raw and naive solution to automatically open an issue every time a new hook is added to the core. Issue will point missing hooks in the available hooks table.
We could exploit a GitHub action to run a python script when pushing in the doc. The script should scan the existing functions in this module and the modules in this folder. Detected functions can be stored in a JSON or something (e.g. a JSON with a key
new_hooks
, where new hooks are stored each time). If the already stored differ from the detected ones (i.e. a new hook exists), we set an environment variable to be used in a further step of the action. If the env. variable is true, we open an issue with the hooks in thenew_hooks
key.How much dirty is this?