#Repositories
A project can hold its git repositories on Lore. You clone and push them with
plain git over HTTPS, and the lore command answers git when it asks who you
are, so nobody copies a token by hand. A new project can live on Lore with no
other git host; an existing repository can move in, or be copied in from
GitHub and kept up to date.
Repositories need the Build capability, switched in
Settings ▸ General ▸ Capabilities. See
Capabilities. There is no page for code in
the browser yet: a repository is reached with git and the lore command.
#Creating a repository
Only a project Admin creates or deletes a repository. From a shell signed
in with lore login:
lore code repo create api
The repository is empty, and its default branch is main unless
--default-branch names another. lore code repo list prints every
repository of the project with its clone URL:
https://<instance>/<project>/<repo>.git
A repository named like its project is also reachable as
https://<instance>/<project>.git.
#Cloning and pushing
lore clone acme/api
cd api
git push
lore clone <project>[/<repo>] clones the repository and installs the lore
command as git's credential helper for that instance. Without /<repo> it
takes the repository named like the project, or the project's only one. From
then on, git fetch, git pull and git push work as with any other host.
In an existing checkout, lore code remote --add adds the repository as a
remote named lore.
Members push; Viewers clone and read. Deleting the default branch is refused, and so is a push to a repository over its size cap. On a self-hosted Lore, which keeps its repositories on disk, a force-push that rewrites the default branch's history is refused as well; other branches still take one.
#In CI
Set LORE_API_KEY to an API key, and the credential helper answers git with
it. A key narrowed to Clone and fetch repositories and Push to
repositories is all a pipeline needs.
#A commit names a quest
A pushed commit whose message names a quest, #Q123, is recorded on that
quest's commit list, by whoever pushed it. Nothing else is needed: no hook, no
CI step. A commit the quest already lists is not added twice, even when it
was recorded under a shorter sha.
Only commits that reach an existing branch count. Pushing a new branch records nothing until its commits land on a branch that already existed, and an import (below) records nothing at all. Every push appears in the project's activity.
#Moving a repository in
lore code import pushes a checkout into a new or empty repository: the
default branch first, then the other branches and the tags. It needs no access
to the old host, so it works from any clone.
git clone https://github.com/acme/api.git
cd api
lore code repo create api
lore code import api
On Lore's cloud a large history goes in by several pushes of at most 40,000 new objects each, and the command stops before pushing anything if a file is over 32 MiB. Run it again after an interruption: it reads what the repository already holds and carries on. A self-hosted Lore takes everything in one push.
#Keeping a copy of GitHub
A repository whose home stays on GitHub can still have a copy on Lore, so the
lore command and Lore itself can read it. Import it once as above, then add
a step to the pipeline that runs after each merge:
git push https://<instance>/<project>/<repo>.git "$GITHUB_SHA:refs/heads/main"
Push the commit as it is, never with --force: without it, git itself
refuses a push that would rewrite the copy's history.
#Backups
Every night, Lore writes each repository that saw a push as a git bundle into
its object storage, and keeps the last seven. A bundle is one file git clone
reads, so a repository comes back without a running Lore:
git clone code-backup.bundle restored
cd restored
lore code repo create api
lore code import api
A self-hosted Lore with no object storage configured keeps those bundles on its own volume, next to the repositories. See Self-hosting.
#From the command line
| Command | What it does |
|---|---|
lore clone <project>[/<repo>] [dir] |
Clone a repository, with the credential helper installed |
lore code repo list |
The project's repositories and their clone URLs |
lore code repo create <name> |
Create an empty repository |
lore code repo delete <name> |
Delete a repository and everything in it |
lore code remote |
Print a clone URL; --add adds it as a remote of this checkout |
lore code import [<repo>] |
Push this checkout into a new or empty repository |
The full list is in The lore CLI.