GitHub issues and discussions are where developers describe precise problems with the tools they use: missing features, integration gaps, workarounds that do not quite work. For a developer tool, these are some of the most specific signals of need you can find. They are also someone else's workspace, kept by maintainers who did not ask for advertising.
When a reply is welcome
- Someone asks whether a tool exists for a problem, or how others solved it.
- An issue describes a need the project has said it will not address, and your tool does.
- A discussion is explicitly about comparing approaches or tools.
It is usually not welcome on bug reports that the project can fix itself, on pull requests, or anywhere maintainers have asked for focus.
A practical approach
- Read the project's contribution guidelines. Check CONTRIBUTING files, the code of conduct and any discussion rules before commenting.
- Confirm the comment is on topic. Only reply where your tool directly addresses the problem described in the issue or discussion.
- Help with the project first. Suggest a fix or workaround within the project where one exists, before pointing elsewhere.
- Disclose your affiliation. If you mention a tool you built, say so plainly.
- Respect the maintainers. If maintainers ask you not to mention external tools, stop.
GitHub's own acceptable use policies also prohibit spam and unsolicited advertising, so restraint here is both polite and required.
How Distrarc helps on GitHub
For products with a technical audience, Distrarc can search GitHub for relevant issues and discussions and return them with a link, the date and the reason they fit. Reply drafts answer first and disclose your affiliation, and you post them yourself. Separately, you can connect your own GitHub repository after you sign up, so Distrarc can use your code for context and prepare draft pull requests for changes you approve. See sources.
Related: Distrarc for developer tools. Start with a free first report or see pricing.