Start from a repository

Most workspaces start from a Git repository. Harthelm clones it into /data/app, and pulls and pushes go through Harthelm's Git proxy with your connection. Your token stays on the platform and never reaches the workspace.

Connect your Git accountCopy Anchor Link

You do this once per Git provider.

1. Open the account menu at the top right and click Account settings.
2. Open Git connections and click Connect … next to your installation's Git provider.
3. Sign in at the provider and allow access. Back in the console, the row says "Connected as … since …".

hart cannot make a connection; it uses the one you made in the console.

Create the workspaceCopy Anchor Link

The start shows "Cloning the repository". If the repository already has a harthelm.yml, open the Run panel and Sync; see Landscapes.

Commit, pull and pushCopy Anchor Link

Use git in a terminal, or the editor's Source Control view, as usual. The remote origin points at Harthelm's Git proxy, which forwards to the provider with the workspace owner's connection.

• Who you are in Git. Commits made in a terminal carry the name of the person who opened that terminal, and so do commits made with hart exec for its caller. If you type in a colleague's terminal, the console warns you: commits made there carry their name. In the editor, each person commits as themselves, in the Source Control view and in the terminals of their own browser window; the status bar shows the name. Your email goes on a commit only when your sign-in provider verified it; without a verified email only your name is set, and Git takes the email from a git config --global user.email set in a terminal of the workspace (kept with the workspace), or else the workspace owner's verified email. Where no person is known, the editor uses the same global user.name and user.email, or else the workspace owner's. Since 1.2.1; the email rule for terminals and hart exec since 1.2.2.

• Pull. When the branch is behind its upstream, the status bar shows Pull. It fast-forwards /data/app; it never merges. The same from outside:

  Copy Text

  hart git status
  hart git pull

  If the pull changed harthelm.yml, the Run panel offers a Sync.

Reach other repositoriesCopy Anchor Link

A workspace may only reach the repositories on its allow list. Git access on the rail shows them: the origin, with read and write access, and any you added.

1. Open Git access.
2. Under Allow another repository, pick the provider and the repository, and choose Read only or Read and write.
3. Click Allow repository.

Changing the list needs the Editor role, and you must be able to read the repository at the provider yourself.

The workspace ownerCopy Anchor Link

Pulls and pushes use the Git connection of the workspace's owner, at first its creator. If you disconnect your Git account, the workspaces you own can no longer clone, pull or push until you connect again or an admin gives them a new owner. Transfer the ownership under Workspace access; the new owner needs the Editor role and a connection to the same provider.

When it does not workCopy Anchor Link

Next stepsCopy Anchor Link