Keep code changes connected to the work

Connect the tools your team already runs

Link your Git host for branches, commits, and pull requests, and connect Omni so an AI agent can work across Windshift with your permissions.

• GitHub: Connect repositories, branches, commits, and pull requests on github.com or GitHub Enterprise.
• GitLab: Connect repositories, branches, merge requests, and commits on GitLab.com or a self-managed instance.
• Gitea: Connect a self-hosted Gitea installation through its native API.
• Forgejo: Connect Forgejo through its Gitea-compatible API for development links.
• Omni: An open-source, self-hosted AI agent. Omni indexes work items, descriptions, and comments, and runs Windshift MCP tools as actions with each user’s permissions.
• REST API: Read and change Windshift data through documented HTTP endpoints.
• Webhooks: Send Windshift events to automations and systems your organization operates.
• Plugins: Install extensions that add behavior to the Windshift instance you control.

A ticket status does not show what happened in the repository

Without a connection, the work item and the code change become two separate records. Delivery teams have to search branches, commits, and pull requests to reconstruct how the work was implemented.

Windshift keeps those development links on the work item and updates the pull-request state as the change moves through review.

From assigned work to a reviewable change

Start the implementation from the work item and preserve the connection as code moves through review.

• Start with a linked branch: Create a branch from a work item, choose the repository and base branch, and begin with a suggested name containing the item key and title.
• Open the pull request from Windshift: Create a pull request from a linked branch. The work item remains attached to the change throughout review.
• Let item keys create the connection: Windshift detects item keys in branch names, pull-request titles and descriptions, and commit messages.
• Keep review status visible: See related branches, commits, and pull requests on the work item, including whether a pull request is open, merged, or closed.

One delivery record from assignment to review

Developers, reviewers, and delivery teams can follow the same change without rebuilding the connection between tracker and repository.

• Implementation handoff: Move from an assigned item to a linked branch and pull request without manually rebuilding the context. Start a branch from the work item Choose the repository and base branch Begin with a suggested branch name
• Review with context: Open the work item, see the related development activity, and follow the change into the Git host. See branches, commits, and pull requests together Open linked resources in the Git host Check the current pull-request state
• Delivery traceability: Identify which code changes belong to a work item and whether the associated pull request has merged. Trace development activity back to the requirement See the repositories involved in the change Confirm whether linked pull requests have merged

Connect the work to the change

Download Windshift and evaluate the complete handoff from work item to pull request.