HERE TO HELP
Missing a knock?
Let’s take a look.
Start with these common questions.
Feedback about rough edges is welcome, too.
Common questions
Why was there no alert after adding a repository?
The first successful check establishes a quiet baseline. Only new commits discovered later trigger alerts. The default check interval is one minute.
A notification or sound did not appear
Send a test notification and preview the sound separately in Settings. Check macOS permission, alert style, Focus mode, volume and output devices. Test notifications do not play an update sound. Turning sounds off does not disable notifications or monitoring.
The local repository opens, but remote branches fail to load
Branch discovery connects to the real remote. Local folder access does not prove that SSH, a proxy or a credential helper can reach it. Check git ls-remote --heads origin in the same repository. The app does not rewrite SSH or proxy settings.
Why are some commits hidden or silent?
Check the repository’s ignored author list. Ignored commits do not trigger alerts or appear in history, while progress still advances. Expanded history merges all monitored branches and shows shared commits once. Set the displayed entry count from 5 to 20 in Settings.
The store build cannot access an SSH remote
Authorize an existing SSH configuration folder containing a valid known_hosts file. This does not automatically trust hosts or grant access to external keys, proxies or credential helpers. Verify the host in your usual Git tool, then follow the connection guide.
Does it pull code into the working directory?
No. It fetches into app-specific Git refs to detect changes, without pulling, switching branches, merging or changing working files.
Where can it be purchased?
Git Knock is coming to the Mac App Store as a one-time purchase. It is not publicly available yet. The official link will be added to the availability page after release.
Report a problem
For support, email atpking@gmail.com. Include the app version, macOS version, steps, expected behavior and actual result. Screenshots help; hide private repository details and personal or business information first.
Do not post tokens, private keys, complete credential configuration or sensitive code.