warnings for implicit references
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start in alliance_canada/resource_tracking.md at line 3 and inspect the three links named in the build warnings. Update those implicit heading references to explicit references, then run the site build and confirm the warnings no longer appear.
Written by the indexing model from the issue text.
Description
I'm getting a few warnings at build time:
⚠️ alliance_canada/resource_tracking.md:3 Linking "using-the-metrix-portal" to an implicit heading reference, best practice is to create an explicit reference.
Explicit references do not break when you update the title to a section, they are preferred over using the implicit HTML ID created for headers.
⚠️ alliance_canada/resource_tracking.md:3 Linking "tracking-resource-usage-at-an-account-level" to an implicit heading reference, best practice is to create an explicit reference.
Explicit references do not break when you update the title to a section, they are preferred over using the implicit HTML ID created for headers.
⚠️ alliance_canada/resource_tracking.md:3 Linking "requesting-resources" to an implicit heading reference, best practice is to create an explicit reference.
Explicit references do not break when you update the title to a section, they are preferred over using the implicit HTML ID created for headers.
- Dominant language
- Python
- Stars
- 0
- Forks
- 3
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SIMEXP/simexp.github.io
-
update teamOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SIMEXP/simexp.github.io#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SIMEXP/simexp.github.io#14 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
SIMEXP/simexp.github.io#46 ·
-
add a section on nearline usage to the DRAC resourcesMay be free again @bpinsard claimed this 35 days ago, and no pull request is open. Open
SIMEXP/simexp.github.io#45 · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SIMEXP/simexp.github.io#41 · 1 reaction ·
All issues in SIMEXP/simexp.github.io
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
john-kurkowski/tldextract#382 ·
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
feder-cr/invisible_playwright_mcp#1408 ·
Maintainers usually reply within 1 day