Connect GitHub

Export your Forkpoint tasks as GitHub issues. Your Personal Access Token is encrypted at rest and never shown back after saving.

What you need

• A GitHub account.
• A Personal Access Token (PAT) with the repo scope. You will create one in the next step.

The repo scope is required for both public and private repositories. public_repo on its own is not enough — private repos will fail to load.

Part 1: Create a Personal Access Token

1. Open https://github.com/settings/tokens/new?scopes=repo. The repo scope is pre-checked via the link.
2. Fill in Note with a name like Forkpoint so you can identify it later.
3. Pick an Expiration. For production use, 90 days or a custom date is a sensible balance between security and rotation overhead.
4. Confirm the repo scope is checked. Do not uncheck it.
5. Click Generate token.
6. Copy the token immediately. GitHub shows it only once.

Part 2: Add your credentials to Forkpoint

1. Go to /profile/integrations and click Configure on the GitHub card.
2. Fill in the form:
   • Personal Access Token: paste the token you just generated.
   • GitHub username: your login handle, for example octocat.
3. Click Connect GitHub.

Part 3: Test the connection

On the connected view, click Test connection. A success toast with your username confirms that GitHub accepts the token and that Forkpoint can list your repositories.

Part 4: Set a default repository (optional)

Once connected, a searchable repository picker appears. Type to filter by owner or repo name, then click a result to pin it as the default (for example acme/backend). Forkpoint pre-selects this repo each time you export, so you can skip the picker. Click Clear to remove the default and be prompted at export time instead.

Private repos are listed with a lock icon next to the name.

Part 5: Export options

Two checkboxes under Export options control what GitHub receives with each exported issue:

• Include milestones when exporting: Forkpoint milestones are created (or matched by title) on the target repository and linked to the issue.
• Include labels when exporting: tags from your estimation are applied as GitHub labels on the issue. Missing labels are created on the repository.

Changes are saved automatically the moment you toggle them.

Troubleshooting

• 401 Unauthorized: the PAT was revoked, expired, or has a typo. Generate a new one and paste it again.
• 403 Forbidden / “Check your PAT scopes (needs repo)”: the token was accepted but lacks the required scope. Go back to github.com/settings/tokens, delete the old token, and create a new one with the repo scope checked.
• Private repositories missing from the picker: the repo scope is required. public_repo will only list public repositories. Generate a new token with repo and reconnect.

Next

• Connect Jira if you also want to export to Jira projects.
• Connect Slack to be notified when tasks are exported.
• See the full getting started walkthrough for the end-to-end flow.

External reference: GitHub — Managing your personal access tokens.