Documentation / The IDE

Git and CI/CD

A full Git client, conflict resolution, and Jenkins, GitHub Actions, GitLab CI and CloudBees pipelines inside the IDE.

Yuli ships a full Git client and a continuous integration panel. Everything runs in the background: a commit, a push or a pipeline query never blocks the editor.

Git

What you can do

Area Features
Changes Per-hunk stage and discard, staged and unstaged list (or tree), filter.
Commits Details of each commit, branches and graph log.
Comparison Inline or side by side.
Conflicts Three-pane editor with an explained suggestion from the agent.
Tools .gitignore editor, preferences and Git console.
Remote Credential management and sync card.

The Git changes window

  • Navigate with ↑ and ↓.
  • Space stages or unstages the selected file.
  • Discard or open in the editor from the same header.
  • Ctrl+Enter commits (or Commit and push).
  • Large checkboxes per file and per folder, with a partial state, to include or leave out entire projects in one click.

Always up to date, with no background polling

  • Status refreshes when project files change.
  • What the agent does and what you do from an external terminal is reflected instantly.
  • The fetch from the remote only happens when you ask for it with its button. The card shows when it was last queried.
  • Commit, push and pull run in the background, with an indicator visible from anywhere in the IDE and a notice when they finish.

Robustness

  • Recovers on its own after the machine sleeps.
  • Reads have a time limit and show the elapsed time.
  • If the limit expires, Retry appears instead of hanging.

Internal servers

Yuli accepts internal servers over HTTP or with self-signed certificates or certificates from an internal authority. It always asks you for confirmation and remembers the decision per server.

The agent does not commit, push, merge or create branches on its own. Git is only enabled if you explicitly ask for it, and every action requires approval. See Sandbox and permissions.

Commit convention

The team's commit convention is defined in Team settings and can be made mandatory. Commits made by Yuli never carry AI attribution: the author is always the person responsible.

CI/CD

Open it from the left rail: More tools → CI/CD — Jenkins, GitHub Actions, GitLab CI and CloudBees. While it's open, its icon moves up to the rail.

Providers

Provider What you see
GitHub Actions Runs, jobs, logs and artifacts.
GitLab CI Pipelines, jobs and logs.
Jenkins Folders, multibranch projects, pipelines, build history, live console and stages with their own log.
CloudBees CD/RO Read-only deployments: pipelines, environments, applications, releases and the Kubernetes workload.

Common features

  • Pipeline status in the status bar and next to each commit.
  • Native notification when it finishes, even if the IDE is minimized.
  • Log viewer that jumps to the first error. File and line paths open the editor.
  • Explain & fix with the agent on a failed job.
  • Manual runs with parameters, cancellation and artifact downloads.

Jenkins in detail

  • Approve or abort input steps.
  • Stop, enable and disable jobs.
  • Progress percentage per stage and overall, estimated from the duration of previous builds.
  • The console and the pipeline view toggle with a Back button.

CloudBees CD/RO

Configure it in Tools → MCP Servers… with an API token or with your account. Access is verified before saving.

You can choose between two scopes:

  1. Whole account: you see the same as in its web console and open the deployments of any project you want.
  2. One project only: project, pipelines, environments and, optionally, the Kubernetes namespace and selector of the workload.

Sensitive configuration values stay hidden. The agent uses the same read-only connector and can't step outside the chosen scope.

Create a pipeline

Create CI detects the project type (Maven, Gradle, npm or Rust) and generates the matching pipeline file. Pipelines generated by Yuli run the same quality gate as the Git hooks. See Gate and Governance Center.

Development certificates

Next to the address of each CI server and each MCP server there is a checkbox to trust its certificate. If the connection is rejected because of the certificate, the checkbox is highlighted, and checking it retries immediately.

Credentials

Git, CI, MCP and SonarQube tokens and passwords are stored in the system keychain. They never appear in plain text on screen.