Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Anyway to centralize the configuration?#1170

Answeredbyjetersen
edalzell asked this question inQ&A
Discussion options

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?

You must be logged in to vote

The default behavior without creating a config file in the repository is to read it from the user/organization's.github repository.

See this examplehttps://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
Note here there are no confighttps://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.

Replies: 2 comments 2 replies

Comment options

I guess I could put all the configuration in the action? But the config is still needed to "trigger" this action, right?

You must be logged in to vote
0 replies
Comment options

The default behavior without creating a config file in the repository is to read it from the user/organization's.github repository.

See this examplehttps://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
Note here there are no confighttps://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.

You must be logged in to vote
2 replies
@justinmchase
Comment options

Note this doesn't work in enterprise github when your.github repo is set tointernal. The defaultGITHUB_TOKEN does not have permissions to read from that repo and unless you want to create a pat which can and write all repos in the org, or create a custom pat for every repo you're out of luck.

@jetersen
Comment options

I believe GitHub documents the.github as an must be public.

At least according to this doc:https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file

But ya if you want a private/internal repo you need to use a different PAT or github app to authorize.

Answer selected byjetersen
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
3 participants
@edalzell@justinmchase@jetersen
[8]ページ先頭
©2009-2025 Movatter.jp