Skip to main content

Validate repository standards and speed up repository imports

· 3 min read
Venue.sh Team
Venue.sh Team
Venue.sh

This release expands Scorecards to validate repository files, makes multi-repository imports faster to configure, and improves how you explore Development Insights through dashboards and the Assistant.

Validate repository content with Scorecards​

Scorecards can now check the files inside your repositories as well as catalog entity metadata. Use repository-content rules to verify that required files exist or that matching files contain the expected configuration.

  • Repository targeting - Apply a rule to selected repositories or repositories linked to specific catalog entities.
  • Flexible authoring - Start from a category template, describe your goal for assisted generation, or write match and content expressions manually.
  • Live preview - Review matching files and pass or fail outcomes before you save a rule.
  • Catalog visibility - See repository-content results alongside other Scorecards results on a repository's catalog page.
  • Clearer expressions - Use shared operators for file paths, file names, extensions, existence checks, and file content.

For example, you can create rules that check whether package.json exists, whether a repository contains unit tests, or whether configuration files include an expected setting.

See Scorecards for the available authoring methods and Expressions for syntax and examples.

Apply shared metadata during repository imports​

When you import multiple repositories, you can now apply common metadata from one place during the configuration step.

  • Bulk metadata - Set shared Kind, Owner, Lifecycle, Namespace, and Tags values for all selected repositories.
  • Non-destructive updates - Only completed bulk fields are applied, so empty fields do not overwrite values already configured for individual repositories.
  • Per-repository control - Continue editing individual rows after applying shared values.

See Importing Repos for the complete import workflow.

Explore Development Insights more easily​

Development Insights now gives you more context in the dashboard list and more ways to ask about delivery performance.

  • Dashboard descriptions - View each dashboard's description directly in the dashboard list.
  • Assistant answers - Ask about DORA, Engineering Overview, and Engineering Throughput and Cycle metrics in natural language.
  • Filter-aware results - Include a project, time range, priority, issue type, or DORA report year in your prompt to scope the answer.

For example:

  • "What is our deployment frequency this quarter?"
  • "How does our lead time for changes compare to last month?"
  • "Summarize throughput and cycle time for the platform project."

You need Development Insights read permission and the feature enabled for your organization. See Development Insights and Assistant for details.

More reliable Assistant and dashboards​

This release also improves day-to-day reliability:

  • Visible reasoning - When you use a supported Claude model with thinking enabled, the thinking panel appears while the response is streaming.
  • Stable dashboard sections - Development Insights dashboards no longer fail while restoring saved collapsed-section preferences.
  • Consistent controls - Development Insights date controls now follow the surrounding layout without a fixed height.

See Also​