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

🛠 Tooling: Use the GitHub API to set up more project settings #83

Closed
3 tasks done
JoshuaKGoldberg opened this issue Dec 6, 2022 · 0 comments · Fixed by #130
Closed
3 tasks done

🛠 Tooling: Use the GitHub API to set up more project settings #83

JoshuaKGoldberg opened this issue Dec 6, 2022 · 0 comments · Fixed by #130
Labels
area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this!

Comments

@JoshuaKGoldberg
Copy link
Owner

Bug Report Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have pulled the latest main branch of the repository.
  • I have searched for related issues and found none that matched my issue.

Overview

#82 added usage of the gh GitHub CLI for a few project settings. But there are a few areas of project settings not doable just through that:

  • Checking Automatically delete head branches
  • Checking Limit how many branches and tags can be updated in a single push
  • Configuring branch protections
  • Disabling Wikis
  • Required CI jobs

Those should also be set up for repositories, so you don't have to do it manually.

Additional Info

I'd like to use octokit.js or some equivalent to also set those up in scripts/setup.js.

@JoshuaKGoldberg JoshuaKGoldberg added area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this! labels Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant