Is it necessary to create settings file in every repository?

[mitchboulay]

Hi,
I have my repository settings configured in org/.github/.github/settings.yml and I am trying to configure such that on repository creation, each repository will automatically inherit the configuration.

Is this possible, or is is expected that for each repo that I want to inherit settings, I must add a .github/settings.yml & _extends?

[gr2m]

No need to create a .github/settings.yml in each file. The app inherits the setting from the [org]/.github repository by default

[gr2m]

Unfortunately no, the app needs to have file read access in order to read the configuration, at least on private repositories. I think public repositories should work to read configuration without the need to install the app

[mitchboulay]

But I have that under my app configuration? Regardless of whether my org/.github repo is public or private, the settings are only being invoked when that .github/settings.yml file extends .github.

[gr2m]

If your repository has a .github/[app].yml file, then you need to set the _extends key. If the file is not present, it will be loaded from [org]/.github at .github/[app].yml

See https://github.com/probot/octokit-plugin-config/#the-_extends-key

If that still doesn't work for you I'll try to replicate the problem with a new app

[mitchboulay]

Okay, you are correct, I was able to get that to work as I can see the homepage URL appears to be pulling in and team configuration is applying. Have you, last one, any particular reason why branch rules wouldn't be inherited?

Below are my rules, again if I use the _extends key it works:

[mitchboulay]

Please disregard. I created another repository and added a readme.md file on creation. I've gathered the following for this to work as I was expecting:

1. Settings must be defined prior to repository creation
2. Select option to add README.md so that the main branch is published and settings can be applied.

Thank you for your help with this @gr2m !