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 .github/settings.yml #145

Merged
merged 3 commits into from
Apr 22, 2024
Merged

Add .github/settings.yml #145

merged 3 commits into from
Apr 22, 2024

Conversation

chartgerink
Copy link
Member

@chartgerink chartgerink commented Apr 18, 2024

We recently installed the GitHub settings application to the epiverse-trace organization. This PR adds the relevant .github/settings.yml file that will then become part of any future repo's built on the template.

This PR must be reviewed, as it also has consequences for this repository that need to be resolved first (see below). The settings are my first best guess as to what we want, based on existing settings from the repositories that I investigated. These are only a departure point for our discussion here 💙

Questions

  • The settings set wiki + discussions to false by default - this repo has content in both. Depending on whether we want to disable the wiki + discussions by default, how do we deal with the discussion and wiki that currently exist here?

.github/settings.yml Outdated Show resolved Hide resolved
.github/settings.yml Outdated Show resolved Hide resolved
@@ -0,0 +1,22 @@
repository:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good if we can also set the GitHub Pages settings in accordance with our pkgdown workflow. Let's keep an eye on repository-settings/app#609.

branches:
- name: main
# https://docs.github.com/en/rest/reference/repos#update-branch-protection
protection:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI:
We have discussed using required_linear_history: true with @bahadzie in the past but didn't come up with a satisfying solution.
The problem is that it will not remove the button "update branch" (implied: with a merge commit), but then block you from merging the PR is you clicked this button.

@chartgerink chartgerink merged commit fcc611b into main Apr 22, 2024
1 check passed
@chartgerink chartgerink deleted the add/settings branch April 22, 2024 07:02
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

Successfully merging this pull request may close these issues.

2 participants