Commit Keys
Record fix submissions automatically with one issue key in the commit message
Table of Contents
What are commit keys?
Put an issue key in your commit message and QA Note detects it via the push webhook, recording the fix submission automatically. It piggybacks on something developers already do (committing), so there's no dashboard to open just for record-keeping. Works without any AI coding tool.
bash
git commit -m "fix: handle expired login session (QANOTE-42)"
How it works
- Check your project's issue key prefix (e.g.
QANOTE) in project settings. Every issue gets a unique key likeQANOTE-42. - Include the issue key in your fix commit message and push.
- The GitHub App's push webhook detects the key, transitions the issue to fix submitted, and links the commit to the issue.
- Commit links appear on the issue detail and in maintenance reports.
Deploy confirmation → ready to verify
A recorded commit doesn't mean it's verifiable yet. QA Note correlates deploy events (Vercel, GitHub deployments) with commits, and marks an issue "ready to verify" only after the fix commit has actually shipped. Verifiers never make a wasted trip to staging.
Prerequisites
- GitHub integration (GitHub App installed)
- For deploy correlation, Vercel integration or GitHub deployment events
Tips
- Multiple issue keys in one commit link them all.
- Agents working via MCP are automatically instructed to include issue keys in commit messages — the record survives as long as either path (MCP or commit key) is alive.