Keep project work in sync with GitHub
Engineering work is easiest to follow when the project plan and the code tell the same story. Without a direct connection, teams spend time copying issue updates, pull request links, review state, and delivery progress between systems.
The FortyOne GitHub integration connects GitHub organizations and repositories to your workspace. Link a repository to a FortyOne team, choose whether issues flow into FortyOne or sync in both directions, and keep code activity attached to the project work it advances.
Branches, commits, pull requests, reviews, and checks can update the FortyOne record and drive configurable workflow rules, while branch formats and magic words keep the connection predictable for developers.
Pull request linked
Engineering activity on the story
Story
ENG-214 · Improve search
Review
1 approval
Issue sync
Repository connected to a team
Repository
fortyone/projects
Team
Engineering
Where FortyOne helps
| Benefit | Why it matters |
|---|---|
| One record for delivery | Keep issues, branches, commits, pull requests, reviews, and checks connected to the corresponding FortyOne story. |
| Less duplicate updating | Use inbound or bidirectional issue sync instead of manually copying changes between GitHub and FortyOne. |
| Automatic workflow signals | Move work when branches, commits, pull requests, reviews, or checks reach the events your team configures. |
| Consistent developer handoff | Use workspace branch formats, story identifiers, pull request context, and commit keywords across repositories. |
Connect GitHub issues to the right team
After the FortyOne GitHub App is installed, workspace administrators can choose a repository and link it to a FortyOne team. New and updated issues can then become project work with repository context attached.
Use inbound-only sync when GitHub should be the source for issue changes, or bidirectional sync when supported title, description, and state changes should move between GitHub and FortyOne.
| Setup choice | What it controls |
|---|---|
| GitHub App | Connect an organization and the repositories approved during installation |
| Repository link | Map one repository to the FortyOne team that owns its work |
| Inbound only | Bring GitHub issue changes into FortyOne |
| Bidirectional | Keep supported issue and FortyOne story changes synchronized |
Keep code activity attached to the work
Include a FortyOne story identifier in a branch name, commit, or pull request context to connect engineering activity with the work item. The story can then show the links and delivery state without requiring a manual status report.
FortyOne can also prefill pull request descriptions with story details, link commits using magic words, synchronize supported assignee and label changes, and record review or check state for the linked pull request.
Branch and commits
Linked through the story identifier
Branch
joseph/ENG-214-improve-search
Commit
Part of ENG-214
Pull request
Delivery state visible in FortyOne
Review
Approved
Assignee
Linked FortyOne user
Let engineering events move the workflow
Every team can decide which GitHub events should change a story's workflow status. A branch can mark work as started, a review can move it into review, and a merged pull request or closing commit can complete it.
The automation stays explicit: administrators choose the event, optional base-branch pattern, and target FortyOne status. That keeps repository behavior aligned with each team's workflow instead of applying one global rule everywhere.
| GitHub event | Example workflow effect |
|---|---|
| Branch created | Move linked work into the configured active status |
| Pull request opened | Reflect that implementation is ready for review |
| Review or check activity | Move work when the team's review conditions are reached |
| Merge or closing keyword | Complete the story using the team's configured rule |
Questions about the GitHub integration
Can I limit which repositories FortyOne can access?
Yes. GitHub shows the permissions requested by the FortyOne GitHub App and lets the installer choose all repositories or selected repositories.
Do GitHub issues have to sync both ways?
No. Each repository link can use inbound-only sync or bidirectional sync, depending on which system should accept supported updates.
Can GitHub activity update a FortyOne workflow?
Yes. Teams can configure workflow rules for supported branch, commit, pull request, review, check, and merge events.
What GitHub data does FortyOne keep?
FortyOne stores installation and repository metadata plus the issue, pull request, branch, commit, review, check, and comment data needed for linked work and automation. The Privacy Policy explains retention and deletion choices.