Pipelines

GitHub Actions runs and GitLab pipelines, with the job log streaming under its row.

The Pipelines section lists GitHub Actions workflow runs and GitLab pipelines for the repository, with their commit metadata resolved so a run is identifiable by what it built rather than by a number.

Runs, stages and jobs load as you open them rather than all at once, and the section refreshes itself while you are looking at it.

The log opens under the job's own row, keeping the runner's colours and its timestamps.

The job log

Selecting a job expands its log under its row, in the list, rather than in a separate window. While the job is running the log streams.

The runs themselves are identified by what they built rather than by a number: Innesta resolves each run’s commit in your own repository and shows its subject and author beside the run.

What it keeps, rather than flattening:

  • terminal colours, so a failure is still red;
  • timestamps;
  • log levels;
  • the provider’s own section markers, so a folded group is still a group.

The macOS find bar searches it, and it is truncated at a bounded size — a job that produces two hundred megabytes of output does not become the app’s memory problem.

Which hosts

GitHub and GitLab, through their APIs, and only when the repository’s active remote is one of them.

Bitbucket and Azure DevOps are not supported here: there is no API lookup for them, only links.