This thread contains a patchset. You're looking at the original emails, but you may wish to use the patch review UI. Review patch

[PATCH sr.ht-docs] Fix internal links under /builds.sr.ht/

Message ID
DKIM signature
Download raw message
Patch: +8 -6
 builds.sr.ht/build-ssh.md |  4 ++--
 builds.sr.ht/manifest.md  | 10 ++++++----
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/builds.sr.ht/build-ssh.md b/builds.sr.ht/build-ssh.md
index f1b85f6..71d4283 100644
--- a/builds.sr.ht/build-ssh.md
@@ -19,5 +19,5 @@ bash-5.0 $

In addition to connecting to failed builds over SSH, you can add `shell: true`
to your [manifest](manifest.md) to always enable SSH access. Then, you'll be
able to interact with your build as it runs.
to your [manifest](/builds.sr.ht/manifest.md) to always enable SSH access. Then,
you'll be able to interact with your build as it runs.
diff --git a/builds.sr.ht/manifest.md b/builds.sr.ht/manifest.md
index 681ef14..6a0434e 100644
--- a/builds.sr.ht/manifest.md
@@ -71,7 +71,7 @@ page](/builds.sr.ht/compatibility.md) for details.
Whether to keep the build VM alive after all of the tasks have finished, even if
it doesn't fail, so you can SSH in. You can also SSH in before the tasks have
finished and tail the output of the build in your terminal. [Learn more about
SSH access to build VMs](build-ssh.md).
SSH access to build VMs](/builds.sr.ht/build-ssh.md).

## sources

@@ -82,9 +82,11 @@ build environment. Optionally, prefix the protocol with the source control
management scheme, to specify a protocol other than git. Examples:

- `https://git.sr.ht/~sircmpwn/scdoc`: git over https
- `git@git.sr.ht:~sircmpwn/scdoc`: git over SSH ([requires key](private-repos.md))
- `git@git.sr.ht:~sircmpwn/scdoc`: git over SSH
    ([requires key](/builds.sr.ht/private-repos.md))
- `hg+https://hg.sr.ht/~sircmpwn/scdoc`: Mercurial over https
- `hg+ssh://hg.sr.ht/~sircmpwn/scdoc`: Mercurial over SSH ([requires key](private-repos.md))
- `hg+ssh://hg.sr.ht/~sircmpwn/scdoc`: Mercurial over SSH
    ([requires key](/builds.sr.ht/private-repos.md))

## tasks

@@ -117,7 +119,7 @@ Each task is run in a separate login session, so if you modify the groups of the
A list of triggers to execute post-build, which can be used to send emails
or do other post-build tasks.

See also: [Build triggers](triggers.md)
See also: [Build triggers](/builds.sr.ht/triggers.md)

## environment

Review patch Export thread (mbox)