share .github/cpp-linter.yml in .github org repo #61
Replies: 2 comments
-
I'm not sure how feasible this is. We don't have support for a cpp-linter config file (as that is the use case for release-drafter and stalebot). Furthermore, to implement support for a config file that could be scoped to a GitHub organization (the .github repo), we would need to add that to cpp-linter-action logic. Our cpp-linter-action's input are not that complex (though they are getting numerous), and this idea might be better served by a reusable workflow crafted by (and tailored to) a GitHub organization. I used this idea for the nRF24 org (see nRF24's custom reusable workflow). |
Beta Was this translation helpful? Give feedback.
-
I like your implementation using reusable workflow 👍 this is also very elegant to achieve the same functionality. |
Beta Was this translation helpful? Give feedback.
-
This idea just comes to my mind if user wants to have a global configuration file
cpp-linter.yml
located in.github
repo. (similar to release-drafter.yml and stale.yml)I'm just here to record the idea.
Beta Was this translation helpful? Give feedback.
All reactions