github-community-projects / github-community-projects/safe-settings

Warning: possible change in GH API may cause issues with safe-settings

Open
#255 6 comments 2 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
921
Forks
226
Avg merge
18h 3m
Merged PRs (30d)
14

Description

On latest versions:

When a change is triggered and safe-settings runs for a repository, the first change made is for repository settings. Something like

```
DEBUG (mark): GitHub request: PATCH https://api.github.com/repos/ORG/REPO - 422
auto_init: true
visibility: "internal"
has_issues: false
has_projects: false
has_wiki: false
allow_squash_merge: true
allow_merge_commit: false
allow_rebase_merge: false
allow_auto_merge: true
delete_branch_on_merge: true
org: "REDACTED"
```

This request, however, has started to fail with the below message:

`"data":{"message":"Visibility is already internal.","documentation_url":"https://github.com/pricing"}}`

In case its relevant: this request also has the nebula header enabled `"headers":{"accept":"application/vnd.github.nebula-preview+json"`

I do not know where/how to track down possible changes to GH API that might cause this :/

cc @decyjphr

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.