Skip to main content

Validate repository standards and speed up repository imports

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

Scorecards can now check the files inside a repository as well as its catalog metadata. Multi-repository imports let you set shared metadata once instead of row by row. And you can ask the Assistant about delivery performance in plain language.

Validate repository content with Scorecards​

Use repository-content rules to verify that required files exist, or that matching files contain the configuration you expect.

  • Repository targeting - Apply a rule to selected repositories or repositories linked to specific catalog entities.
  • Three ways to author - Start from a category template, describe your goal for assisted generation, or write match and content expressions by hand.
  • 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 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, set the metadata they share from one place during the configuration step.

  • Bulk metadata - Set shared Kind, Owner, Lifecycle, Namespace, and Tags values for every selected repository.
  • Non-destructive updates - Venue.sh applies only the bulk fields you filled in, so empty fields leave per-repository values alone.
  • Per-repository control - Keep editing individual rows after applying shared values.

See Importing Repos for the complete import workflow.

Explore Development Insights more easily​

  • Dashboard descriptions - Read each dashboard's description in the dashboard list.
  • Assistant answers - Ask about DORA, Engineering Overview, and Engineering Throughput and Cycle metrics in natural language.
  • Filter-aware results - Name 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​

  • Visible reasoning - When you use a supported Claude model with thinking enabled, the thinking panel appears while the response streams.
  • 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 instead of holding a fixed height.

See Also​