Replies: 1 comment 3 replies
-
Heya, yes its not intended that you specifically link to MyST provides functionality to link between files in a more "agnostic" way, either (recommended) you explicitly create a target to a heading. (mytarget)=
# My heading Then you can refer to this with or you can use implicit tagets with: https://myst-parser.readthedocs.io/en/latest/syntax/optional.html?highlight=anchor#auto-generated-header-anchors |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
i'm adding the jupyter book link checker to our build. I ran into this previously where it identifies broken links internally that should be ok and do work locally.
Here is an example. i do use an include here and added a scope.md file update that should make the link to
#package-categories
resolve correctly but it's still finding errors. Is the link checker looking at pyopensci.org/contributing-guide/link-hereOr is it resolving to the localhost where it's built?
or am i creating links incorrectly?
[package fit within identified categories for the pyOpenSci ecosystem](../open-source-software-peer-review/aims-and-scope.html#package-categories/)
CI build here:
https://github.com/pyOpenSci/contributing-guide/actions/runs/3101475747/jobs/5022875383#step:6:46
NOTE: i provided an example with an include file however i'm seeing the same behavior for other internal links.
many thanks for any guidance. id love to be able to check links before publishing. The alternative will be something like html proofer i suppose.
Beta Was this translation helpful? Give feedback.
All reactions