Streamlining GitHub Custom Properties: Enhancing Repo Tracking and Admin Workflow

GitHub's custom properties feature offers powerful capabilities for enriching repositories with vital information—from compliance frameworks and data sensitivity to specific project details. This functionality is crucial for effective repo tracking and streamlined administration. However, a recent discussion in the GitHub Community highlights significant user experience (UX) challenges that could hinder its full potential and impact overall developer productivity.

The Challenge: Asymmetric UX and Navigation Hurdles

The discussion, initiated by user jsoref, points out several critical issues regarding the discoverability and navigation of custom properties settings. The core of the problem lies in the perceived asymmetry between organization-level and repository-level custom properties pages.

• Confusion in Field Definition: jsoref notes that it's "very easy for someone to land on repository custom properties and not realize that they need to go to organization custom properties in order to define fields." This distinction, while logical from a permissions standpoint, creates a confusing initial experience for users trying to configure these properties.
• Misleading Navigation from Org Settings: When viewing a list of repositories with custom properties at the organization level, clicking on a specific repository's name currently directs users to the repository's main page, not its custom properties settings. This forces an extra navigation step, adding friction to the administrative workflow.
• Missing Backlink from Repo to Org Definitions: There's no direct link from a repository's custom properties page back to the organization-level definitions. This absence can be particularly frustrating for users who need to reference or edit the overarching field definitions, even if they don't have direct write access to them. jsoref emphasizes that even in such cases, providing a view-only link would prevent "failing API calls" and improve the user journey.

GitHub's Response: Seeking Deeper Understanding

The GitHub Properties team, represented by GlebIrovich, quickly engaged with the feedback, acknowledging the potential for confusion. They sought further clarification on jsoref's specific workflows and use cases. GlebIrovich questioned why an organization administrator, with permissions to set values directly from the organization settings page, would prefer to navigate to individual repository settings to perform these actions. This inquiry underscores GitHub's commitment to understanding the real-world scenarios that drive user expectations and pain points.

Impact on Developer Productivity and Repo Tracking

While seemingly minor UX details, these navigation and discoverability issues can accumulate into significant productivity drains for administrators managing numerous repositories. Efficient repo tracking relies on quick and intuitive access to repository metadata. If setting up or reviewing custom properties is cumbersome, it can delay crucial compliance checks, data sensitivity assessments, or project categorization—all of which are vital for maintaining organizational standards and even informing aspects of a developer performance review by providing context on project scope and requirements.

The ability to easily define, apply, and view custom properties across an organization is fundamental for scaling development practices and ensuring data governance. Improving this experience would not only enhance administrative efficiency but also empower teams to leverage GitHub's features more effectively for better project management and oversight.

Community's Role in Shaping the Future

This discussion exemplifies the power of community feedback in refining developer tools. By sharing detailed observations and use cases, users like jsoref provide invaluable insights that guide product development. The GitHub team's proactive engagement further demonstrates how critical these conversations are for building a platform that truly serves its diverse user base. We encourage more developers and administrators to contribute their experiences to help shape the future of GitHub's custom properties and other features.