Skip to main content

​
Workspace

In this tab, you can:
  • Edit your Product Overview, which helps Macroscope understand your product better.
  • Add or remove email recipients from your team’s weekly digest emails.

​
Account Settings

In this tab, you can toggle on/off features like:
  • Automatically adding PR summaries to your GitHub PR descriptions
  • Custom code review rules
  • Minimum severity thresholds for code review comments
  • Slack @mention preferences — choose whether Macroscope @mentions you directly (e.g. when you’re assigned as a reviewer) or references your name without @mentioning you

​
Repo Settings

Repos Settings Per repository, you can toggle on/off features like:
  • Automatic code review
  • Auto-assigning a reviewer when a PR is opened without a reviewer assigned
  • Always-review labels that trigger code reviews even when automatic review is off
  • Skip labels that prevent code reviews on matching PRs
You can apply settings across multiple repositories simultaneously.

​
Release Ref Patterns

Release Ref Settings Here is where you can tell Macroscope which refs count as releases. This helps Macroscope know what commits should be classified as released commits, so Macroscope can generate better summaries and AMA responses.
The Release Ref Patterns field can take multiple inputs. Inputs can be glob patterns.A glob pattern for a GitHub release branch depends on the naming convention used for those branches. Here are some common patterns and their corresponding globs:
  1. Simple release/ prefix
If all release branches start with release/ followed by a version or identifier, you can use: release/*This will match branches like release/v1.0, release/hotfix-2.1, but not release/feature/new-feature.
  1. release/ prefix with nested segments
If your release branches might have further sub-segments (e.g., release/v1.0/rc1), you can use: release/**This will match release/v1.0, release/v1.0/rc1, release/v2.0/alpha/test.
  1. Version-specific patterns
If your release branches follow a semantic versioning pattern like release/vX.Y.Z, you can use a more specific glob: release/v[0-9].[0-9].[0-9]*This would match release/v1.2.3, release/v10.5.0, but not release/v1.0-rc.
  1. Pre-release or specific release types
If you have specific pre-release branches (e.g., release/v1.0-rc, release/v2.0-beta), you can combine patterns: release/v*..-rc*This would match branches like release/v1.0.0-rc1.

​
Connections

This is where you can configure your connections to Slack, Linear, Jira, BigQuery, PostHog, and LaunchDarkly. Learn more about how to integrate Macroscope with your issue management systems. Webhooks are coming soon — you’ll be able to trigger Macroscope queries from external services like Zapier, n8n, or your own APIs.

​
Support

This is where you can set up a shared Slack channel with the Macroscope Support Team, which you can use to ask questions and share feedback directly. In the rare event that your repositories and other data in Macroscope fall out of sync with GitHub, you can click the Synchronize with GitHub button to manually have Macroscope resynchronize with GitHub.