[Feature Request] : Allow to mark (tag) actions and execute them selectively according to their markers (tags).

Hi!

The (custom) markers (tags) would allow defining “which” (groups of) actions to execute. Just as the stages allow to define “when/where” the actions are executed (in relation to git)

I personally prefer to separate some actions in different categories or according to certain modalities.

• Examples:

  • [check]: actions that check things.

  • [fix]: actions that modify things (and that could break things)

  • [stable]: less likely to break things - more stable or robust actions - such as some formatters.

  • [experimental]: more likely to break things - less stable, less robust or a bit more experimental actions - such as some autofixers.

  • [strict]: more restrictive modalities or configurations, like some linters, type checkers or tools that remove things.

• Example:

pre-commit run --all-files --markers=strict,stable,check

Thanks! .

[asottile]

I am intentionally not implementing that because extension is a hard problem that you really don’t need and makes caching difficult / intractable

there are many other issues which mention this

I am well aware of other tools which do this and it does not improve the argument

[diegovalenzuelaiturra]

Ok, I understand …

One last question (I’m not totally sure if this is a way to accomplish the same thing)

• @asottile , Do you think it would be useful to allow overwriting and/or extending configuration files? I think this can avoid duplication of configurations, in cases where multiple configurations are already being used.

Currently, tools such as docker-compose ^docker-compose-extends ^docker-compose-cli or hydra-core ^hydra-core (through omegaconf ^omegaconf) allow defining base configuration files (also allowing the use of variable interpolation ^omegaconf-variable-interpolation)

• which can be overwritten or extended by additional configuration files
• or populated for example using environment variables or other
• and whose values can be overwritten by arguments provided through the command line

Thanks!