github-community-projects / github-community-projects/safe-settings
The `auto_init: true` option is not working
- Dominant language
- JavaScript
- Stars
- 921
- Forks
- 226
- Avg merge
- 18h 3m
- Merged PRs (30d)
- 14
Description
## Problem Description
We have safe-settings hosted in our GitHub organization using serverless framework. When an empty repo is created it does not inherit the global settings hosted in our admin repo. As a test, I created:
* test-repo-empty
* test-repo-empty-with-readme
Additionally, we also run safe-settings on a [cron lambda](https://github.com/github/safe-settings/issues/313). After a readme was created on `test-repo-empty` the cron lambda picked it up and successfully applied the global settings.
### What is actually happening
The `test-repo-empty` repo was unmodified.
The `test-repo-empty-with-readme` repo inherited the global settings.
### What is the expected behavior
Both repos inherit the global settings.
### Error output, if available
There was no error in the logs.
## Context
### Are you using the hosted instance of probot/settings or running your own?
We are running our own hosted instance using serverless framework.
### If running your own instance, are you using it with github.com or GitHub Enterprise?
We are using it with github.com
#### Version of probot/settings
2.0.7
#### Version of GitHub Enterprise
N/A
Contributor guide
Assessment
This issue has not been assessed yet.