Link Checker Report

Open
#230 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions
Domain
documentation

Research direction

Start with the three listed RST files and compare their repeated netCDF documentation links. Review the linked GitHub Actions output and rerun the link checker after determining the appropriate link changes; done means the five reported errors are resolved without introducing new broken links.

Written by the indexing model from the issue text.

Description

automated issue report

Summary

Status Count
🔍 Total 75
✅ Successful 59
⏳ Timeouts 0
🔀 Redirected 11
👻 Excluded 0
❓ Unknown 0
🚫 Errors 5
⛔ Unsupported 0

Errors per input

Errors in docs/details/interface_support.rst
Errors in docs/userdocs/user_guide/data_objects.rst
Errors in docs/userdocs/user_guide/general_topics.rst

Redirects per input

Redirects in docs/change_log.rst

Full Github Actions output

Dominant language
Python
Stars
16
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SciTools/ncdata

All issues in SciTools/ncdata

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.