Skip to main content

Share to GitHub

Use Share to GitHub when you want to turn evidence from NEXT into a GitHub issue without rewriting the context by hand.

GitHub sharing is configured at the teamspace level. You create one or more GitHub connections in Settings → Integrations, then choose the right connection when you share a chat, highlight, or cluster.

Before You Start​

  • Open the teamspace where you want to configure the GitHub connection.
  • Make sure GitHub issues are enabled in the repository you want to use.
  • Make sure you can create issues in that repository.
  • Have the repository URL ready, for example https://github.com/your-organization/repo.

Steps to Connect (One-Time)​

  1. In NEXT, open Settings → Integrations → GitHub.
  2. Click Connect.
  3. Create a new connection and give it a clear name, such as GitHub - Bugs or GitHub - Product.
  4. Enter the repository URL and save the connection.
  5. Repeat this setup for any additional repositories you want to use.

Steps to Share​

  1. Open the chat, highlight, or cluster you want to share.
  2. Click Share and choose GitHub.
  3. Select the GitHub connection you want to use.
  4. Review the share text and confirm the share.

NEXT creates a GitHub issue in the configured repository and includes a link back to the source in NEXT.

When Should I Use GitHub?​

  • Use GitHub when your product or engineering team tracks work as GitHub issues.
  • Use separate GitHub connections when different teams need issues routed to different repositories.
  • Use GitHub when you want the evidence link from NEXT attached to the work item from the start.

Tips​

  • Name each connection after the destination it represents so the right repository is easy to choose at share time.
  • Keep the issue title short and specific, then use the description to add context.
  • If you regularly send different kinds of work to different repositories, create multiple connections instead of reusing one repository for everything.

Troubleshooting​

  • GitHub is not available in the share menu. Connect GitHub first in Settings → Integrations → GitHub for the current teamspace.
  • The share fails with an authorization or permission error such as 401 or 403. Make sure the connection is still valid and that you can create issues in the target repository.
  • The share fails because issues are disabled. Enable Issues in that repository or use another repository with issues enabled.
  • The issue appears in the wrong repository. Check the selected GitHub connection and confirm that its repository URL is correct.
  • Bulk sharing starts failing after many requests. GitHub rate limits API usage, so spread out large batches if you automate this workflow heavily.

FAQ​

Q: What does NEXT send to GitHub?​

NEXT creates a GitHub issue using the content from the item you shared and adds a link back to the source in NEXT.

Q: Can I use more than one GitHub repository?​

Yes. You can create multiple GitHub connections and choose the right one each time you share.

Q: Why does GitHub sharing fail even though the connection exists?​

The most common causes are missing issue permissions, the wrong repository URL, or GitHub issues being disabled for that repository.

Only people who already have permission to view that item in NEXT.

Q: Does NEXT upload the video file to GitHub?​

No. NEXT shares the written content and a link back to the source in NEXT.