Basics
RepoDraft
Support
RepoDraft Support
Help for local repository selection, All Changes and Staged Only analysis, draft types, editing, copying, and local Git signal review.
Before you email
A short checklist helps support answer faster.
Use these notes to keep the request specific while leaving private repository details out of the message.
Analysis
Name the scope you used.
Say whether the issue happens with All Changes, Staged Only, or both, and include the draft type selected.Steps
Describe what happened.
List the steps to reproduce, what you expected, and what RepoDraft showed instead.Screenshots
Use sanitized screenshots only.
Attach a screenshot only after your email app opens, and remove private source code, raw diffs, private paths, private client names, secrets, tokens, API keys, and credentials first.AI
Does RepoDraft use AI?
No AI service is used for core drafting. RepoDraft prepares drafts from local Git state and supported local technology signals.Uploads
Does RepoDraft upload repositories?
Core features do not upload repositories, source code, diffs, file paths, repository metadata, or generated drafts.Git hosting
Does it require GitHub, GitLab, or Bitbucket login?
No. Core drafting works from local repositories and does not require a Git hosting login.Commits
Does RepoDraft commit or push changes?
No. RepoDraft is not an automatic commit tool. It prepares draft text for you to review, edit, copy, and use intentionally.Editing
Can I edit before copying?
Yes. Drafts are starting points. Review the detected signals, edit the wording, then copy only the text you want to use.Support request
What should I include?
Include the macOS version, RepoDraft version if known, analysis scope, draft type, Git repository state, steps to reproduce, and a sanitized screenshot if helpful.Contact
Contact RepoDraft support
The support email builder opens your email app with a structured draft. The website does not send or store the message.
Contact support
Build a support email
Create a structured note for the studio. The website does not send or store this form; your email app sends the message.
If the builder is unavailable, email dev@hazybyte.studio.
Do not include passwords, payment details, private source code, private diffs, full folder listings, or sensitive file paths. Attach screenshots only after your email app opens.