diff options
| author | berfr <me@berfr.me> | 2020-03-01 14:14:28 -0500 |
|---|---|---|
| committer | Drew DeVault <sir@cmpwn.com> | 2020-03-02 11:28:10 -0500 |
| commit | da6fc834cc22d087148de1c197d4cd7cf15e9e03 (patch) | |
| tree | 12855ba2ffc060cca367324c4f536bbf7bd7ee9a /builds.sr.ht | |
| parent | 8d981c707aae20f461806288bc929f4fae8a6524 (diff) | |
| download | sr.ht-docs-da6fc834cc22d087148de1c197d4cd7cf15e9e03.tar.gz | |
Fix internal links under /builds.sr.ht/
Diffstat (limited to 'builds.sr.ht')
| -rw-r--r-- | builds.sr.ht/build-ssh.md | 4 | ||||
| -rw-r--r-- | builds.sr.ht/manifest.md | 8 |
2 files changed, 7 insertions, 5 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 +++ b/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 09792eb..de744b1 100644 --- a/builds.sr.ht/manifest.md +++ b/builds.sr.ht/manifest.md @@ -90,9 +90,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 @@ -125,7 +127,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 |