Fix broken relative links
For some obscure reason yet to be identified, *some* (not all) relative links that use "../" to reference parent items in the repository point to invalid URLs. This may be an issue with the rendering process from markdown to html. Replace relative links with absolute ones. Signed-off-by: Robin Jarry <robin@jarry.cc>
This commit is contained in:
parent
0d76ec9e5b
commit
dd23f69a6f
|
@ -21,8 +21,8 @@ Here are some good resources:
|
|||
|
||||
We do have some general resources for learning how to use git the sr.ht way:
|
||||
|
||||
- [Using git-send-email for sending and reviewing patches on sr.ht](../git.sr.ht/send-email.md)
|
||||
- [Code review with lists.sr.ht](../lists.sr.ht/code-review.md)
|
||||
- [Using git-send-email for sending and reviewing patches on sr.ht](/git.sr.ht/send-email.md)
|
||||
- [Code review with lists.sr.ht](/lists.sr.ht/code-review.md)
|
||||
|
||||
# SSH host keys
|
||||
|
||||
|
@ -146,8 +146,8 @@ far.
|
|||
|
||||
# Referencing tickets in git commit messages
|
||||
|
||||
If your source repository is linked to a [project](../hub.sr.ht/index.md), you
|
||||
may interact with [todo.sr.ht](../todo.sr.ht/index.md) tickets via specific git
|
||||
If your source repository is linked to a [project](/hub.sr.ht/index.md), you
|
||||
may interact with [todo.sr.ht](/todo.sr.ht/index.md) tickets via specific git
|
||||
commit [trailers](https://git-scm.com/docs/git-interpret-trailers). The trailer
|
||||
values must be valid URLs to tickets. Any other value will be ignored.
|
||||
A comment will be inserted in the referenced tickets with a back-link to the
|
||||
|
|
|
@ -400,7 +400,7 @@ Deletes this [subscription resource](#subscription-resource).
|
|||
### /api/user/...
|
||||
|
||||
Webhook for user events. Includes the [standard webhook
|
||||
endpoints](../api-conventions.md#webhooks)
|
||||
endpoints](/api-conventions.md#webhooks)
|
||||
|
||||
#### email:received
|
||||
|
||||
|
|
|
@ -18,8 +18,8 @@ We have some resources for you:
|
|||
|
||||
If you plan on contributing patches, we also have these guides:
|
||||
|
||||
- [Using git-send-email for sending and reviewing patches on sr.ht](../git.sr.ht/send-email.md)
|
||||
- [Using hg-email for sending and retrieving patches on sr.ht](../hg.sr.ht/email.md)
|
||||
- [Using git-send-email for sending and reviewing patches on sr.ht](/git.sr.ht/send-email.md)
|
||||
- [Using hg-email for sending and retrieving patches on sr.ht](/hg.sr.ht/email.md)
|
||||
|
||||
# lists.sr.ht manual
|
||||
|
||||
|
|
|
@ -8,8 +8,8 @@ conventions](/api-conventions.md).
|
|||
|
||||
## Authentication
|
||||
|
||||
Authentication is done via the [meta.sr.ht OAuth
|
||||
flow](../oauth-api.md). The following OAuth scopes are available for meta.sr.ht:
|
||||
Authentication is done via the [meta.sr.ht OAuth flow](oauth-api.md). The
|
||||
following OAuth scopes are available for meta.sr.ht:
|
||||
|
||||
- **audit:read**: read the security audit log
|
||||
- **keys:read**, **keys:write**: read & update user SSH & PGP keys
|
||||
|
|
|
@ -445,7 +445,7 @@ implies the authenticated user.
|
|||
### /api/user/...
|
||||
|
||||
Webhook for user events. Includes the [standard webhook
|
||||
endpoints](../api-conventions.md#webhooks)
|
||||
endpoints](/api-conventions.md#webhooks)
|
||||
|
||||
#### tracker:create
|
||||
|
||||
|
@ -504,7 +504,7 @@ The new [event resource](#event-resource).
|
|||
### /api/user/:username/trackers/:tracker-name
|
||||
|
||||
Webhook for tracker events. Includes the [standard webhook
|
||||
endpoints](../api-conventions.md#webhooks)
|
||||
endpoints](/api-conventions.md#webhooks)
|
||||
|
||||
#### label:create
|
||||
|
||||
|
|
Loading…
Reference in New Issue