Support custom properties for Github repositories
complete
Matan Grady
Add support for custom properties https://docs.github.com/en/rest/repos/custom-properties?apiVersion=2022-11-28#get-all-custom-property-values-for-a-repository
Matan Grady
complete
This is now available! check our docs
https://docs.port.io/build-your-software-catalog/sync-data-to-catalog/git/github/examples/resource-mapping-examples#map-repositories-and-repository-custom-properties
Available immediately for all existing Github integrations
Matan Grady
in progress
S
Simon Beaulieu
Having support to fetch custom properties would help us reduce the amount of data we have to ask users to put in a YAML file in each repository that we ingest in Port.
One benefit is less custom/manual validation to do given that custom properties can be defined at the org level and have a strict structure around what values they can contain.
It would also benefit our security team who needs to have a high-level overview of repository configurations/classifications which ties into our internal compliance processes.
E
Etienne Jacquot
We also are using the custom properties in our company for the same use cases, and track the ownership of the Github repositories in the organization. Having this support could help to integrate the repositories in Port more efficiently.
M
Mark Tarry
We have been using Github Custom Properties as a method to distinguish between repositories which follow:
* Deployment methodologies: continuous delivery vs manual
* Sonar configurations: e.g. single project vs mono-repo with multiple projects
* Deliverables: service vs library vs "other"
We further then use these Custom Properties to drive repository rulesets (i.e. automation within GitHub).
Ingesting this metadata into Port would be very useful. For example:
- Building scorecards to target only mono-repos
- Limiting self-service actions to only repos not currently using continuous delivery
- Generating metrics based on the number of repos with specific attributes, broken down by team