-
I'd like to use this for all my laravel packages, and have the same config for each package. Is there a way to centralize the configuration? I know I can call actions from a repo, but how do I tell release-drafter to use a configuration file that's in a centralized repo? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
I guess I could put all the configuration in the action? But the config is still needed to "trigger" this action, right? |
Beta Was this translation helpful? Give feedback.
-
The default behavior without creating a config file in the repository is to read it from the user/organization's See this example https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml You can also explicitly use |
Beta Was this translation helpful? Give feedback.
The default behavior without creating a config file in the repository is to read it from the user/organization's
.github
repository.See this example https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
Note here there are no config https://github.com/jenkinsci/gitlab-branch-source-plugin/tree/master/.github but if you check the workflows folder it uses release drafter
You can also explicitly use
_extends
which supports pointing to another config within the same repository or another repository entirely.