Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt

Use this file to discover all available pages before exploring further.

GitHub is a practical engineering source in the current app. The live form captures one repository at a time so the first rollout stays easy to validate.

​
Current connection form

The current GitHub source form asks for:
  • Connection Name
  • Repository Owner
  • Repository Name
  • Personal Access Token
  • The token field accepts personal access tokens such as ghp_... or github_pat_....
  • Each connection is scoped to one repository owner and one repository name in the current form.

​
Good first use cases

  • engineering metrics and delivery reporting
  • release and commit reporting for one product repository
  • joining PR activity with incident or deployment data downstream

​
Before you connect

  • Create a GitHub token with the repository access your team approves.
  • Confirm the exact owner and repository name before testing.
  • Choose one resource such as pull_requests or issues for the first validation run.

​
Step by step

  1. Open Connections and click + New Connection.
  2. Keep the role set to Source and choose GitHub.
  3. Fill the form with real values, for example:
    • Connection Name: Platform App Repo
    • Repository Owner: northstar
    • Repository Name: platform-app
    • Personal Access Token: github_pat_...
  4. Click Test Connection and save only after the test succeeds.
  5. Create a pipeline and start with one high-value resource so validation stays simple.

​
Resources available in the current source preview

  • issues
  • pull_requests
  • stargazers
  • events
  • commits
  • releases
  • branches
  • tags
  • contributors
  • milestones
  • labels
  • forks

​
Real-world example

An engineering operations team syncs GitHub pull_requests, issues, and commits from northstar/platform-app into PostgreSQL so delivery metrics can be combined with deployment and incident data.

​
Troubleshooting

  • If the test fails, re-check the owner, repo, and token permissions.
  • If expected records are missing, confirm whether the repository is private or restricted by organization policy.
  • Keep the first rollout to one repository per connection so debugging stays clear.