Skip to content
GitmoapdocsBeta
Tutorial· Can you show me?

Your first repository, end to end

0 of 5 steps doneRemembered in this browserStart

Overview

Go from a signed-in account to a repository with your code in it and a pipeline that runs on it. Every step ends with something you can see in the web app, so you always know the last one worked before you start the next.

You will install the command-line tools, create a repository, push to it from your own machine, and add a pipeline. Nothing here asks you to choose: where there is a choice, the step makes it for you, and the guide it links to covers the alternatives.

Before you start

  • A Gitmoap account.Signing up gives you a personal namespace under your username, and that is where this repository lives. You own it, so you already hold every access level the steps need.
  • git on your machine.Any recent version works.
  • A terminal, for the install and the push. Everything else happens in the web app.

Steps

  1. Install the command-line tools.

    Follow Install the command-line tools for your platform and stop after its last check: gitmoap doctor reporting no failures is the signal to carry on.

  2. Create the repository.

    In the web app, choose Create in the top bar, then New repository. Leave your personal namespace as the group, name the repository hello-gitmoap, and choose Create repository. You land on the empty repository, which shows the commands for pushing to it.

  3. Push your first commit.

    In a terminal, make a folder with one file in it and push it, putting your own username in place of <your-username>:

    shellscript
    mkdir hello-gitmoap && cd hello-gitmoap
    git init -b main
    echo "# hello-gitmoap" > README.md
    git add README.md && git commit -m "First commit"
    git remote add origin gitmoap://<your-username>/hello-gitmoap
    git push -u origin main

    The repository's page in the web app swaps its push instructions for your code: the README renders on its home page, and Commits lists the commit you just made.

  4. Build a pipeline.

    Choose Pipelines in the repository's side navigation, then New pipeline. Drag a capability from the palette onto the canvas, and choose Create once the issues panel at the bottom is empty. Pipelines covers triggers, stages and wiring in full.

  5. Run it.

    Open the pipeline, choose Run pipeline, pick main, and choose Run pipeline again. You land on the run, with each step's log streaming as it goes. When it finishes green, you have the whole loop: code in, pipeline run, result back.

Next steps

  • Merge requestspropose a change on a branch and have it reviewed before it lands on main.
  • Repository rulesprotect main, so that every change reaches it through a merge request.
  • Access tokensgive a script or a build a credential of its own instead of your sign-in.