# GitHub issue template contact links to discussions and security

> Use GitHub issue-template contact links to push support questions and security reports onto the right routes before they become the wrong kind of issue.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-issue-template-contact-links-to-discussions-and-security/
- Source: [docs.github.com](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)
- GrowthDex source hub: [GitHub Docs: Configuring issue templates for your repository](/sources/github-docs-configuring-issue-templates-for-your-repository-docs-github-/)
- Last checked: 2026-06-05T14:05:00Z
- Rarity: rare
- Budget: free
- Channels: GitHub, Community, Security
- Stages: queue routing, security intake, community support, issue deflection


## Why this can grow

Not every incoming problem belongs in the public issue queue. A product question may belong in Discussions, and a security report absolutely should not be handled like a normal bug thread. GitHub's `contact_links` setting gives the issue chooser alternate destinations with names, URLs, and short explanations. That turns the chooser into a routing layer instead of a dead-end form list. The result is less queue pollution, fewer accidental public disclosures, and a better first experience for contributors who simply chose the wrong door.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where github issue template contact links to discussions and security can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the GitHub and Community channel.
3. Use the evidence from docs.github.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

GitHub's example `config.yml` routes community support to Discussions and security vulnerabilities to the GitHub Security Bug Bounty page using `contact_links` entries with `name`, `url`, and `about` fields.

## Adjacent tactics in the same lane

- [GitHub issue template chooser with blank issues disabled](/growth-ideas/github-issue-template-chooser-with-blank-issues-disabled/) - same source, 2 shared channels
- [GitHub security policy link before public bug report](/growth-ideas/github-security-policy-link-before-public-bug-report/) - 2 shared channels, 1 shared stage
- [GitHub release asset verification in install docs](/growth-ideas/github-release-asset-verification-in-install-docs/) - 2 shared channels
- [GitHub profile README as operator proof surface](/growth-ideas/github-profile-readme-as-operator-proof-surface/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The issue intake should finish the sorting first](/blog/the-issue-intake-should-finish-the-sorting-first/) - community-led growth, support deflection, seo

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.