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

Add initial configuration to Gihub repository #342

Open
yuval-linker opened this issue Feb 12, 2021 · 3 comments
Open

Add initial configuration to Gihub repository #342

yuval-linker opened this issue Feb 12, 2021 · 3 comments

Comments

@yuval-linker
Copy link

When a user selects to create a Github repository it could be beneficial to have the option to give an initial configuration to the repo. Like needing a review on every pull request to merge.

@rjherrera
Copy link
Member

@yuval-linker I agree, this would be a nice addition. I'm not sure if the gem we use to generate repos in GitHub allows this kind of configuration, but it would be nice to enforce the reviewers thingy alongside the automatic deletion of stale branches. We could have a "standard config" for our recommended way to handle repositories.

@rjherrera
Copy link
Member

I think enforcing reviewers is not possible with octokit, but deleting branches on merge is. It is undocumented in the gem, but available in the API, I don't think it is a risk because it is an option and options are passed directly to the post request to the api, so we would use it like this:

Octokit::Client.new(access_token: access_token).create_repository('some_repo', delete_branch_on_merge: true)

what do you think @agomezcampero

@agomezcampero
Copy link
Contributor

I think it would be a good addition specially for Platanus. I wouldn't add the configurations as a user option, but rather enforce some basic options we currently use. In my opinion there are enough questions already while creating a new project and adding Github repo options seems a bit excessive, adding a few options that are not too specific sounds like a good idea.

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

No branches or pull requests

3 participants