Repository Custom Properties Feedback #69914
Replies: 63 comments 110 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.
-
Should we be able to use the It would be great to be able to do this so I can batch edit the security settings of repositories with a particular property value. |
Beta Was this translation helpful? Give feedback.
-
When will https://api.github.com/search/repositories support filtering by custom properties? When using a query like The same query does work on https://github.com/search?type=repositories |
Beta Was this translation helpful? Give feedback.
-
One thing that would be a huge help for my company is custom properties that can be set as “required” but without a default value. Required properties without a default would work like this:
|
Beta Was this translation helpful? Give feedback.
-
Response #2 |
Beta Was this translation helpful? Give feedback.
-
I suggest integrating custom properties with the We've been managing repository metadata with repository topics. Then we moved to custom props from topics but we need keep sync from custom props to topics for some cases. |
Beta Was this translation helpful? Give feedback.
-
What does the roadmap look like for custom properties? We are interested in array values for properties so that we can track monorepos that would have multiple valid values for some properties. |
Beta Was this translation helpful? Give feedback.
-
Response #20457 |
Beta Was this translation helpful? Give feedback.
-
The List custom property values for organization repositories REST API isn't returning property values for all repositories. I noticed that some of our archived repositories aren't returning any property values in that API call. There's no documentation to suggest archived repositories are omitted (it just states "Lists organization repositories") and anecdotally it seems as though some repositories have values returned, while others do not. API calls are being made via Octokit: I then made a call to Any ideas? Should I file a support ticket? |
Beta Was this translation helpful? Give feedback.
-
When modifying a repository using the API, there is no way to modify the custom_properties attribute even if you can set that attribute at repo creation: https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#update-a-repository. Is there a plan to add that capability in the following weeks? I would need this very soon. |
Beta Was this translation helpful? Give feedback.
-
Some of the uses we previously had for topics make a lot of sense as custom properties. But there is one downside: anyone with read access can see topics, but only admins (maybe maintainers as well?) can see custom properties in the UI. Could custom properties be exposed in a similar way to topics? Perhaps with a per-property setting. |
Beta Was this translation helpful? Give feedback.
-
The space on the custom properties page is poorly used. It seems to favour long property names instead of long values which makes it quite useless for "project details". For example, if you want to link to somewhere (for example, where CI runs), the URL gets cut off and there is a lot of wasted space that could have been used to show the full value. |
Beta Was this translation helpful? Give feedback.
-
Will this feature be moved to Github Enterprise Server? THX |
Beta Was this translation helpful? Give feedback.
-
It would be nice to use this properties for the Copilot Content Exclusion Filter. THX |
Beta Was this translation helpful? Give feedback.
-
It would be fantastic to be able to display these props in the about page, as a way to communicate common organization data across teams. I imagine the visibility could be set at organization or repo level. |
Beta Was this translation helpful? Give feedback.
-
I’m excited to announce that Repository Custom Properties are GA! 🎉
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