Explore repository activity insights
Activity Overview shows who changed what in your Salesforce repository, which components change most, and where knowledge or test coverage is thin.
Overview
Source Code Repo Insights turns your Git history into answers about your Salesforce delivery. It has three tabs:
- Activity Overview — who, what, where and how concentrated. This article covers it.
- Promotion and Change Narrative — covered in Track promotions and the change narrative.
Activity Overview is computed from commits stored in MetaLens360, not fetched live. That is what makes a 90-day view instant. You choose which branches to sync, and every later sync only fetches what is new.
Before you start
- Connect a Git repository. See Connect a Git repository.
- Plan for the first sync to take a few minutes on a busy repository. It reads about two calls to your Git provider per commit.
Steps
- Open Source Control → Source Code Repo Insights and stay on Activity Overview.
- Choose a Repository and, optionally, a branch.
- If you see "No commit history stored yet", click Choose branches to sync. Otherwise click Sync branches… to add or update branches.
- In the Sync branches dialog, tick the branches you want. If a promotion pipeline exists, its stage branches are already selected.
- Click Sync {n} branch(es). The sync runs on the server, so you can click Run in background and keep working. Reopen the dialog at any time to check progress.
- Pick a time window — 30d, 90d, 180d or 365d.
- Click Refresh when a "new commits since" chip appears, to recompute the view with the newest history.
What you see
| Tile or panel | What it tells you |
|---|---|
| Commits, Contributors, Components touched, Lines, Active days | Volume and pace of change in the window. Contributors are counted by who wrote the change, not by an automation account that merged it. |
| Concentration | How much of the work sits with a few people. |
| Most-changed components | Hot spots that change often and may need refactoring or extra review. |
| Changes together | Component pairs that keep changing together — often a hidden dependency. |
| Single-owner components | Components changed repeatedly by only one person — a knowledge risk. |
| Apex changed without a test | Commits that touched Apex but no test file. |
| Branch activity | Activity per synced branch. |
Example
Priya opens Activity Overview for acme/salesforce-core over 90d. Single-owner components lists QuoteTrigger, changed 40 times by one developer. She schedules a pairing session so a second person learns it before the next release.
FAQs
Why don't I see a branch in the tabs?
Only branches with stored history appear. Sync the branch from Sync branches…, or let a promotion sync fetch it.
Do I need to keep syncing manually?
You can sync on demand at any time. To keep branches current automatically, add them to a schedule — see Schedule automatic syncs.
Does this page show deployments?
No. It reports what happened in the repository. For where a change has reached, use the Promotion tab.
Troubleshooting
"That branch is already being synced. Wait for the running sync to finish."
A sync for that branch is in progress. Reopen Sync branches… to watch it, then refresh.
"Sync failed. Check the repository connection and its token."
MetaLens360 could not read the repository. Test the connection in Connections. See Fix Git repository access.
"No commits in this window."
Choose a longer window, or check that the selected branch has been synced.
Related articles
Was this article helpful?
Related articles
- Track promotions and the change narrativeSee where each change has reached in your promotion pipeline, what is blocked or stranded, and ask plain-English questions about what changed and where it is live.
- Set up a promotion pipelineDescribe how code moves through your branches and Salesforce environments so MetaLens360 can track where every change has reached and what is stuck.
- Connect a Git repositoryAdd a GitHub, Bitbucket or Azure DevOps repository with a read-only token so MetaLens360 can correlate deployed metadata with commits and branches.
- Fix Git repository accessResolve errors when MetaLens360 can't list branches or read commits from a connected repository — expired tokens, missing scopes, SSO authorization and wrong owner names.