During todays meeting we talked about potentially having downstream tools like augur (that are using this tool to analyze repos) be able to dynamically detect which label the maintainers have specified as applying to AI usage by parsing the github actions config.
since the config gets committed to the repo in a known location, we can use non-platform-dependent methods to read this config, taking that responsibility away from downstream analysis tools and giving it to the app itself. This way the cli can return something sensible, like JSON, for projects that integrate this CLI to make use of to easily find out what label each individual repo uses for their AI flag(s) when conducting analysis
this is getting very meta/self-referential though and may be confusing for newcomers regarding the line between platform independent code and the actions wrappers and things. so documenting this clearly might be hard
During todays meeting we talked about potentially having downstream tools like augur (that are using this tool to analyze repos) be able to dynamically detect which label the maintainers have specified as applying to AI usage by parsing the github actions config.
since the config gets committed to the repo in a known location, we can use non-platform-dependent methods to read this config, taking that responsibility away from downstream analysis tools and giving it to the app itself. This way the cli can return something sensible, like JSON, for projects that integrate this CLI to make use of to easily find out what label each individual repo uses for their AI flag(s) when conducting analysis
this is getting very meta/self-referential though and may be confusing for newcomers regarding the line between platform independent code and the actions wrappers and things. so documenting this clearly might be hard