-
Notifications
You must be signed in to change notification settings - Fork 736
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
Custom properties missing in GHRepository #1847
Comments
PR welcome. |
I've got a working local poc for GET /repos/{owner}/{repo}/properties/values and have started exploring the POST for create or update. @bitwiseman, do you have advise on how I should architect this? The response body of the GET and request body of the POST are slightly different and custom properties also exist at the org level. I am considering modeling my Custom Properties solution off of GHHooks. |
@gitPushPuppets |
|
Sounds good
…On Thu, Dec 5, 2024 at 4:08 PM Liam Newman ***@***.***> wrote:
-
***@***.***/rest/orgs/custom-properties?apiVersion=2022-11-28
- Organization custom properties. This same API can also update
repositories in an organization (with some limitations).
-
***@***.***/rest/repos/repos?apiVersion=2022-11-28#create-an-organization-repository
- mentions custom_properties as an optional parameter
—
Reply to this email directly, view it on GitHub
<#1847 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALZT3PXX3A5SW5PQYTGWIN32EDFHVAVCNFSM6AAAAABSRVVY5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRGU3DSMJUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I explored these as well. The custom props are created and designed at the
org level with some nice datatype functionality.
The repos in an org will have all custom properties on them and will either
be null or set to the default value defined by the org props definition.
I started testing using the same object for get and post but github uses
slightly different objects.
GET
[
{
"property_name": "branch-protection-rulesets",
"value": "true"
},
{
"property_name": "team",
"value": "java"
}
]
POST
{
"properties": [
{
"property_name": "branch-protection-rulesets",
"value": "true"
},
{
"property_name": "team",
"value": "java"
}
]
}
|
The child objects looks the same, so that's good. I wouldn't expected the |
Describe the bug
GHRepository
class (interface torepos/org/repo_name
GitHub endpoint) is missing custom properties. They are mentioned in the GitHub documentation at the root level asThe text was updated successfully, but these errors were encountered: