Repository Custom Properties Beta Feedback #69914
Replies: 39 comments 65 replies
-
|
I would like to use Custom Properties to say X devs are maintainers of this repository. To do that, I would need as Type Multi Select. |
Beta Was this translation helpful? Give feedback.
-
|
Wonderful! |
Beta Was this translation helpful? Give feedback.
-
|
I just tried the custom properties and my actions doesn't have record in audit log. |
Beta Was this translation helpful? Give feedback.
-
|
The documentation does not provide many examples of actual use cases for custom properties. You set them up and then what? I guess you can search on them, and apparently you can use them for rulesets (the documentation is pretty vague though. What does it mean to "target" them?). More examples of applied use cases would help. |
Beta Was this translation helpful? Give feedback.
-
|
Are there any plans to include these properties as claims in the GitHub Actions OIDC access token? |
Beta Was this translation helpful? Give feedback.
-
|
The custom props are available to the GH API? It would be nice to filter repos by props. And in the future can we select repos to run required workflows using props, like in the rulesets? |
Beta Was this translation helpful? Give feedback.
-
|
The docs say that we can already filter by property: https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization#searching-and-filtering-repositories-by-custom-properties-values Is this premature? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting... I've been using repository "topics" to automate based on whether the "topic" is there or not... custom properties seems like a much better approach. |
Beta Was this translation helpful? Give feedback.
-
|
I just had a quick go at it:
|
Beta Was this translation helpful? Give feedback.
-
|
It would be cool to filter in a github project on a repository property of an issue |
Beta Was this translation helpful? Give feedback.
-
|
It would be cool to access those properties within workflows like secrets or variables, like |
Beta Was this translation helpful? Give feedback.
-
|
I was going to switch from topics to properties, but apparently you need to be an organization owner to set properties, while topics can be set by maintainers. It would be great to create a permission to set properties for maintainers and above. |
Beta Was this translation helpful? Give feedback.
-
|
Is this available on all GitHub plans? |
Beta Was this translation helpful? Give feedback.
-
|
awesome new feature. here is some additional functionality we would like to see: |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible to consume the repository custom properties to select repository access instead of the drop-down list on a 'Runner Group' great feature by the way |
Beta Was this translation helpful? Give feedback.
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
|
Hi Team, I noticed that when I tried to hit the Custom Property API PATCH https://api.github.com/orgs/{org name}/properties/values, I got a 204 status code even though the repo was not present. I believe that if the repo is not present, we should get a 422 Unprocessable Entity status code. Can someone please look into this and let me know if this is a bug? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if this is a bug, or just an undocumented change but is anyone running into recent issues with permissions for the /repos/{owner}/{repo}/properties/values endpoint? It seems at some point between 27th November 17:00 and 28th November 11:00 (UTC) the permissions changed for this endpoint. Previously a GitHub app with repository contents read and repository metadata read could access the endpoint, now the app gets 403 though the permissions have not changed. It is worth noting the response header 'x-accepted-github-permissions' is now 'repository_custom_properties=read'; I'm not sure if this has changed or not, unfortunately I did not check it before. Just to be sure, I have tested the endpoint with an app that has all the available repository and organisation permissions, read and write or admin where possible. Some details on the request:
And the response:
|
Beta Was this translation helpful? Give feedback.
-
|
Earlier repo admins will be able to see custom properties by going to the URL https://github.com/{org_name}/{repo_name}/settings/custom-properties/, but when I check now, it is throwing a 404 error. Is it a bug or have some changes been made? |
Beta Was this translation helpful? Give feedback.
-
|
Hallo, I get a HTTP 422 Error which says that the Default Value must be empty. Why does this happen? Can I set a default value? In the Docs it is mentioned. |
Beta Was this translation helpful? Give feedback.
-
|
Why haven't I gotten the new feature preview? Is it only certain people on GitHub who get it? , this is an example of an image that has just been updated on GitHub |
Beta Was this translation helpful? Give feedback.
-
|
Will be good to make this navlist useful like GitHub Advisory Database so that we don't click on something that is not useful. |
Beta Was this translation helpful? Give feedback.
-
|
Filtering repository by the custom properties doesn't seem to work? This property is a select list and I've defined it on a bunch of repos, but I'm not getting any results: The filter for this value fails on both the newly-released org repository page, and in the org settings on the screen where I can assign values. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to sort by stars, as well as by "used by". Also it's a bit confusing that i have to select "Forks" to pick "Sources"; it's very non-obvious that i can get to "exclude forks" under "forks". |
Beta Was this translation helpful? Give feedback.
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
|
Would it be possible to view certain properties in the new organizational repository list alongside topics? A custom property could have a “show in repository list” setting. When enabled, the property would appear in the organizational repository list alongside topics. In other words, a colored label with the text “key=value” or “key:value” mixed in with the repo topics. We currently use topics to group our apps and would like to move to exclusively using custom properties. We just need it “visible at a glance” when browsing through our thousands of repositories to get a pulse on what’s happening across the company. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, When creating a ruleset that targets custom properties, no repositories are being scoped for the target. Is this a known issue? |
Beta Was this translation helpful? Give feedback.
-
|
Old code search, can it be restored, someone please reply |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, i know the custom properties can be accessed via the REST API. Is it possible to access them via the GraphQL API? Thank you! |
Beta Was this translation helpful? Give feedback.
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible to add an option in the (beta) repository filter list to allow repository properties that are blank to be selected? A common use case for us is to list repositories missing a value. |
Beta Was this translation helpful? Give feedback.














{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
I’m excited to announce that Repository Custom Properties are in Beta! 🎉
Starting today, organization administrators can create custom properties to enrich repositories with valuable information. Using these properties, you can dynamically target repository rules to apply protections on just your production repositories or to a business unit or any other way you want to classify your repositories.
Checkout the docs to learn more
❔ Still have questions?
Beta Was this translation helpful? Give feedback.
All reactions