Termiyo
Cloud Login
← All solutions

Solutions

CI/CD from GitHub, GitLab or Gitsi

See whether your builds pass on GitHub, GitLab or your own server without leaving the terminal you deploy from.

Termiyo can add a CI workflow to a GitHub or GitLab repository as a pull request or merge request you review — never a direct change — and shows its recent runs as passed, failed or running. For a Gitsi repository on a server you are connected to, it can run the repository’s GitHub Actions workflow on that server after every push. Use it to check your builds from the terminal you deploy from. Setting CI up from Termiyo is part of the paid plans.

Termiyo can add a CI workflow to a repository for you — as a pull request or merge request you review, never a direct change — and shows the latest runs beside it.

Recorded in Termiyo with stand-ins for GitHub and GitLab running on the recording machine, a test token and a test server holding a Gitsi repository. No real repository, account or token appears.

Steps

  1. Open CI/CD and save a token

    Open CI/CD in the menu and pick GitHub or GitLab. Press “Save a new token”, paste a token and press “Save to key box”. Termiyo says which permissions the token needs, and sends it only to that forge.

  2. Name the repository

    Type the repository as owner/name or paste its link, and press “Check”. Termiyo recognises the kind of project and suggests how to build it under “Build it as”.

  3. Set it up, as a pull request

    Press “Set up CI”. Termiyo creates a branch, commits the workflow there and opens a pull request (a merge request on GitLab). Nothing reaches your default branch until someone merges it, and Termiyo never overwrites an existing CI file.

  4. Watch the runs

    Under “Recent runs”, press “Refresh” to see each run as Passed, Failed or Running, with its branch and commit.

  5. Repositories on your own server

    The “Repos on a host” tab lists the Gitsi repositories on a server you are connected to. “Turn CI on” runs a repository’s GitHub Actions workflow on that server after every push you make, with nektos/act in Docker.

Good to know

  • Setting CI up from Termiyo is part of the paid plans. CI that is already set up keeps running whatever your plan, and anyone with access to the repository can still add a workflow by hand.

Transcript

See whether your builds pass on GitHub, GitLab or your own server without leaving the terminal you deploy from.

Save a token, sent only to that forge.

Name the repository, and Termiyo suggests how to build it.

Set-up comes as a pull request you review.

Every run’s result, with its branch and commit, is a press away.

Repositories on your own server get CI that runs where they live.