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

Alternate default repo (not .github) #213

Open
derekmurawsky opened this issue Aug 31, 2022 · 1 comment
Open

Alternate default repo (not .github) #213

derekmurawsky opened this issue Aug 31, 2022 · 1 comment

Comments

@derekmurawsky
Copy link

What’s missing?

Support an alternate default repo to .github via environment variable or other setting.

Why?

Currently this plugin allows for a central / default config to exist in the organization's .github repository. This repository is public by design. This results in information leakage around any configuration options for repositories within the organization and makes auditors nervous (or makes them outright say we can't do this). Examples include teams with certain permissions, users, etc.

Alternatives you tried

None. I can't see a workaround to this other than having settings only in each private repo, which isn't DRY and puts a lot of overhead on the configuration of each repo instead of via a central bot/plugin like this system.

@derekmurawsky derekmurawsky changed the title Alternate default repo Alternate default repo (not .github) Aug 31, 2022
@gr2m
Copy link
Contributor

gr2m commented Sep 5, 2022

The .github has been hard-coded since we introduced the feature in GitHub, I cannot recall anyone asking to make that default configurable. Do you use this library directly or through Probot?

I would not add environmental variable support, that should happen outside of this library.

It's an octokit plugin, so custom parameters would need to be passed to the Octokit constructore, e.g.

new Octokit({ config: { defaultRepository: "my-default-config-repo" }}

For the time being, I'd suggest you fork this plugin and publish your fork for your own usage. Given that nobody asked for this in the past, it's not something that I'd see us prioritize

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants