-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration file outside the repo #28
Comments
That definitely seems like a nice feature to have! I like the So this way, there will be 3 types of paths to config files:
Also, PRs are always welcome :) |
I will do some experimenting... but probably quite slowly 🙂. |
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 |
+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 |
I'll treat this as high priority. PRs welcome :) |
@dave-v in this PR you can provide a local filepath to your configuration. |
@alexschwartz @dave-v @Noamshmueli @rjulius23 more ways to specify config file is now supported in v1.4.0 |
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.
The text was updated successfully, but these errors were encountered: