Skip to content
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

FR: pull from external config #2048

Open
elijaholmos opened this issue Aug 16, 2023 · 2 comments · May be fixed by #2222
Open

FR: pull from external config #2048

elijaholmos opened this issue Aug 16, 2023 · 2 comments · May be fixed by #2222
Assignees
Labels
help wanted We'd love to have community involvement on this issue. priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@elijaholmos
Copy link

As a developer, I would like to have a single, centralized configuration for all projects in my GH org that are using release-please as a GitHub action. There should also be an option to extend this configuration on a per-repo basis, in case certain adjustments need to be made.

Renovate has a good example of how this is implemented in its service. Ideally, I could use an extends field in my release-please-config.json:

{
  "extends": "MyOrgName/.github",
  "packages": { ".": {} },
  "release-type": "node"
}

this would merge the individual repo's configuration with the configuration found in my organization's .github repo, overwriting the parent's configuration with the child's values.

@elijaholmos elijaholmos added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Aug 16, 2023
@chingor13 chingor13 added the help wanted We'd love to have community involvement on this issue. label Sep 7, 2023
@chingor13
Copy link
Contributor

This sounds like a reasonable feature, but not something we have time to prioritize. Note that there are considerations around permissions which could make this more complex.

antongolub added a commit to antongolub-forks/release-please that referenced this issue Feb 12, 2024
antongolub added a commit to antongolub-forks/release-please that referenced this issue Feb 12, 2024
@antongolub antongolub linked a pull request Feb 12, 2024 that will close this issue
4 tasks
@antongolub
Copy link

@chingor13,

I'd like to try. Could you help me with that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted We'd love to have community involvement on this issue. priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants