Features / Git repository integration

Keep repository context close to your WordPress work.

Connect a supported Git provider to browse repository metadata and branches in the workspace. This is repository visibility, not a built-in deployment pipeline.

In practice

How you use it

01

Connect a supported provider

Use the supported token integration for GitHub, GitLab or Bitbucket. Grant only the provider permissions required for the repositories you want to inspect.

02

Sync repository context

Review repository and branch information without confusing a metadata sync with a change to the WordPress filesystem.

03

Keep deployment in your existing flow

Continue using your own deployment process. Linking a Git account does not clone a repository onto a site, push changes or automatically deploy a branch.

Inside the workspace

Keep the work in view.

An actual screen from the IrmaWP demo workspace. The workspace includes sample history; available actions depend on your plan, role and site connection.

Git repository integration

Connect a supported Git provider to browse repository metadata and branches in the workspace. This is repository visibility, not a built-in deployment pipeline.

IrmaWP git repository integration workspace context
Demo workspace · Dark mode
Before you connect

What to know

Which plans include the integration?
Pro and Agency include Git repository integration. GitHub sign-in is a separate authentication option and is not the paid repository feature.
Does SSH give me code history?
The SSH file workflow can inspect Git history where a suitable repository exists on the server. That does not make the provider integration a hosted CI/CD service.

Start with your own sites.

Connect a small portfolio, check the tools you need, and choose the plan that fits your team's work.