pr-title-checker
pr-title-checker copied to clipboard
thehanimo
Configuration file outside the repo
We would like to use this action on many different repos with the same configuration, so it would be nice to define the configuration in a common location and reuse it.
An example is this action: https://github.com/release-drafter/release-drafter#configuration-options (look at the paragraph after the table of options that mentions Probot config). In that case, we are able to put configuration files in a separate repo, and each repo using the action can get its config from there.
Perhaps a simple way could be to allow the configuration_path to accept a URL returning the configuration, or for private repos, providing the repo and filepath in that repo, an appropriate access token, and using the GitHub API to extract file contents.
If you would accept a PR, I might have a go.
That definitely seems like a nice feature to have! I like the configuration_path-being-a-URL approach which will essentially be a public URL. About private repos, would a parameter like is_private or even better, a key along with the URL help?
So this way, there will be 3 types of paths to config files:
- Relative to current repo
- Absolute public URLs
- Absolute private URLs (with a flag/key)
Also, PRs are always welcome :)
Isnt it an option to make the GITHUB_REPOSITORY an input variable ? That way you can specify your template repository where your workflow templates are.
+1
I am trying to use this action as an organization wide required action. And it always look for the config file in the wrong location
@dave-v @thehanimo I unintentionally made a PR that partially addresses this issue: https://github.com/thehanimo/pr-title-checker/pull/36
in this PR you can provide a local filepath to your configuration. we needed shared configuration across all our repos, so we use this action with a prior step that downloads the configuration file.
