Bring business context with external custom properties

You can now seamlessly bring business context about your repositories from an external system of record (e.g., a configuration management database (CMDB), an internal developer portal, or an in-house system) into GitHub with external custom properties. This feature is now in public preview.

Keep business context aligned with its source, with updates managed by your external system. This includes information such as ownership, service tier, lifecycle stage, and compliance status.

Use custom properties when you want to manage this context in GitHub, whether through the UI or APIs. Choose external custom properties when an external system should exclusively own and continuously update that context:

• Read-only in the GitHub UI: Users can’t edit these values in GitHub, preventing conflicting updates across systems.
• Ongoing synchronization: Your external integration uses the external custom properties APIs to keep values current as your source data changes.
• Dedicated namespace: Your integration manages properties under its own prefix, keeping them separate from properties managed by other sources.

You can use external custom properties everywhere you use custom properties today, including repository views, repository filtering, and ruleset targeting. Your existing governance can use the synced business context while your external system remains the source of truth.

Port.io is the first partner to integrate with external custom properties. Read Port.io’s announcement for an overview, or follow the Port.io integration guide to sync your business context to GitHub.

You aren’t limited to partner integrations. Any enterprise can build its own integration using the external custom properties APIs, with fine-grained permissions to control its access. To get started, see Integrating custom properties with an external system.

Join the conversation in the GitHub Community announcements category.