Install MergeMeter in 5 minutes
MergeMeter works through a lightweight GitHub Action that fires every time a pull request is merged. No code changes to your app — just one workflow file and a secret.
Before you begin
A GitHub organization with at least one repository
Owner or Admin access to the repository you want to track
A MergeMeter account (sign in with GitHub — invitation required during private beta)
Sign in and add your organization
Sign in to MergeMeter with your GitHub account. During onboarding you will select your GitHub organization — MergeMeter reads your org membership to set up your workspace. No write access to your code is requested at sign-in.
Add a repository and copy the ingest secret
In your MergeMeter dashboard, navigate to Repositories and add the GitHub repos you want to track. MergeMeter generates a unique ingest secret per repo — copy it, you'll use it in the next step.
Add the secret to your GitHub repository
In your GitHub repository, go to Settings → Secrets and variables → Actions and create a new repository secret named MERGEMETER_SECRET with the value you copied from the dashboard.
Add the GitHub Action workflow file
Create the file below at .github/workflows/mergemeter.yml in your repository. Commit and push to any branch — the action only triggers on merged pull requests.
name: MergeMeter
on:
pull_request:
types: [closed]
jobs:
notify:
# Only run when the PR was actually merged (not just closed).
if: github.event.pull_request.merged == true
runs-on: ubuntu-latest
steps:
- name: Notify MergeMeter
uses: mergemeter/action@v1
with:
secret: ${{ secrets.MERGEMETER_SECRET }}Merge a pull request to verify
The next time a PR is merged in the tracked repository, the Action will fire and send PR metadata to MergeMeter. Within moments, a survey link is generated and sent to the author. Check your MergeMeter dashboard to see the new PR appear in your usage stats.
How it works
PR merged
A developer merges a pull request. The GitHub Action fires and sends the PR metadata — author, title, repo — to MergeMeter via your ingest secret.
Survey delivered
MergeMeter generates a personalized 15-second survey link and delivers it to the PR author. No account or app installation required for respondents.
Confidence recorded
The developer rates their confidence in the change on a 1–5 scale. Responses are anonymous to peers and only aggregated scores are shown to leaders.
Trends surface
Confidence scores accumulate in your dashboard as trend lines, monthly averages, and response rate metrics — giving leaders a data-driven view of team health.
Troubleshooting
The Action ran but nothing appeared in my dashboard.
Verify the MERGEMETER_SECRET value in GitHub Secrets matches exactly what the dashboard displayed. Secrets are case-sensitive and must not include trailing whitespace.
The workflow didn't trigger at all.
Make sure the workflow file is on the default branch and the trigger is set to pull_request with the closed type. GitHub Actions only run workflows that are on the default branch at the time the PR is merged.
I get a 401 Unauthorized error in the Action logs.
The ingest secret is invalid or belongs to a different repository. Rotate the secret from Dashboard → Repositories → your repo → Rotate secret, then update the GitHub Secret value.
Can I track multiple repositories?
Yes. Add each repository in the dashboard to get its own ingest secret, then add the workflow file to each repo with its corresponding secret name.