Configuration file outside the repo about pr-title-checker HOT 8 CLOSED

I will do some experimenting... but probably quite slowly 🙂.

from pr-title-checker.

@dave-v
@thehanimo
I unintentionally made a PR that partially addresses this issue:
#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.

from pr-title-checker.

@alexschwartz @dave-v @Noamshmueli @rjulius23 more ways to specify config file is now supported in v1.4.0

from pr-title-checker.

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:

1. Relative to current repo
2. Absolute public URLs
3. Absolute private URLs (with a flag/key)

Also, PRs are always welcome :)

from pr-title-checker.

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.

from pr-title-checker.

+1

from pr-title-checker.

+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

from pr-title-checker.

I'll treat this as high priority. PRs welcome :)

from pr-title-checker.