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

Feature Request: Enterprise Settings #1199

Open
HariSekhon opened this issue Jun 22, 2022 · 8 comments
Open

Feature Request: Enterprise Settings #1199

HariSekhon opened this issue Jun 22, 2022 · 8 comments
Labels
Status: Pinned A way to keep old or long lived issues around Status: Up for grabs Issues that are ready to be worked on by anyone Type: Feature New feature or request

Comments

@HariSekhon
Copy link

HariSekhon commented Jun 22, 2022

Please support GitHub Enterprise settings, such as:

  • disabling repository creation by members
  • repository forking
  • outside collaborators
  • GitHub Actions:
    • 3rd party actions and workflows allowed (can currently only be done at organization level)
    • read-only workflow permissions by default
  • repository admin permissions for:
    • repo visibility change
    • deletion and transfer
    • issue deletion
  • Biliing spending limits

related to #1200

@HariSekhon
Copy link
Author

GitHub Enterprise support have confirmed the Rest API is deficient, so have raised a public discussions feature request here to track this publicly:

community/community#19570

@kfcampbell
Copy link
Member

I still don't think this behavior is available through the API. The only enterprise APIs I can find are here, which isn't what we're after.

I've inquired about this internally and will report back if I hear anything interesting.

@kfcampbell
Copy link
Member

I've reached out to the API team and they're aware of the request. At the moment this feature request is not being actively worked on and I can't offer a timeline for it, unfortunately.

@liamoneill
Copy link

It appears like some of these settings are present in the GraphQL API (i.e. UpdateEnterpriseAllowPrivateRepositoryForkingSettingInput). Does this provider only use the REST API or would it be possible to use these?

@kfcampbell
Copy link
Member

@liamoneill this provider makes use of the GraphQL API as well! If you'd like to create a PR to support this behavior, please feel free!

@silvan02
Copy link

I also need the option to enable/disable forking

Copy link

👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!

@github-actions github-actions bot added the Status: Stale Used by stalebot to clean house label Apr 21, 2024
@ausfestivus
Copy link

@kfcampbell are you able to put the Status: Pinned label on this to stop it being closed? The feature request still stands.

@github-actions github-actions bot removed the Status: Stale Used by stalebot to clean house label Apr 26, 2024
@kfcampbell kfcampbell added the Status: Pinned A way to keep old or long lived issues around label Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pinned A way to keep old or long lived issues around Status: Up for grabs Issues that are ready to be worked on by anyone Type: Feature New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants