When to use Discussions

Discussions work well when a topic needs community input before it becomes a documentation page or an issue. Keep issue tracking for confirmed bugs and concrete engineering tasks.

Propose a feature

  • Describe the user workflow first.
  • Explain the current workaround.
  • Identify operational or security constraints.
  • State what a successful outcome would change for the team.

Share examples safely

Use synthetic tokens, example domains, and redacted logs in public repositories. A production credential should never be included in a reproduction, even temporarily.

Join a live session

The monthly developer session is the place to ask product questions directly and hear what the team is building.

See community events