Skip to content

Update OpenAPI Descriptions #561

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

Conversation

github-openapi-bot
Copy link
Collaborator

👋 humans. This PR updates the OpenAPI description with the latest changes.

@@ -25414,7 +25416,7 @@
"properties": {
"permission": {
"type": "string",
"description": "The permission to grant the collaborator. **Only valid on organization-owned repositories.** Can be one of: \n\\* `pull` - can pull, but not push to or administer this repository. \n\\* `push` - can pull and push, but not administer this repository. \n\\* `admin` - can pull, push and administer this repository. \n\\* `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions. \n\\* `triage` - Recommended for contributors who need to proactively manage issues and pull requests without write access.",
"description": "The permission to grant the collaborator. **Only valid on organization-owned repositories.** Can be one of: \n\\* `pull` - can pull, but not push to or administer this repository. \n\\* `push` - can pull and push, but not administer this repository. \n\\* `admin` - can pull, push and administer this repository. \n\\* `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions. \n\\* `triage` - Recommended for contributors who need to proactively manage issues and pull requests without write access. \n\\* custom repository role name - Can assign a custom repository role if the owning organization has defined any.",
Copy link
Contributor

Choose a reason for hiding this comment

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

@imwiss the description addition says that permission can be set to a custom role name

custom repository role name - Can assign a custom repository role if the owning organization has defined any.

But the property has an enum that does not permit custom values. It only permits

  • pull
  • push
  • admin
  • maintain
  • triage

I'll file an issue, but wanted to add the comment in context

"/repos/{owner}/{repo}/lfs": {
"put": {
"summary": "Enable Git LFS for a repository",
"description": "**Note:** The Git LFS API endpoints are currently in beta and are subject to change.",
Copy link
Contributor

Choose a reason for hiding this comment

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

@imwiss We would usually add a required preview header for an endpoint like this. For SDK users there is currently no telling that {DELETE,PUT} /repos/{owner}/{repo}/lfs is subjected to change. Should we add a flag to x-github?

@mmrobins mmrobins deleted the openapi-update-9828bb4ef20a33f99a17b4dad564144fcae5e009f8861519638751c536dcfc76 branch May 8, 2023 22:33
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.

3 participants