Link Checker Report

Open
#1,866 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown, ruby
Domain
documentation

Research direction

The broken links are listed under three files: docs/24pullrequests.md, docs/LEARNING.md and reference/implementing-a-concept-exercise.md. Start by opening each file at the line and column numbers in the report and checking whether the target still exists. Done means each listed 404, SSL, or file-not-found link is either fixed or replaced with a working target, and the redirect and archive suggestions are handled for each.

Written by the indexing model from the issue text.

Description

Summary

Status Count
🔍 Total 35
🔗 Unique 34
✅ Successful 26
⏳ Timeouts 0
🔀 Redirected 2
👻 Excluded 2
❓ Unknown 0
🚫 Errors 7
⛔ Unsupported 0

Errors per input

Errors in docs/24pullrequests.md
Errors in docs/LEARNING.md
Errors in reference/implementing-a-concept-exercise.md
  • [ERROR] file:///home/runner/work/ruby/ruby/exercises/concept/README.md (at 17:234) | File not found. Check if file exists and path is correct
  • [ERROR] file:///home/runner/work/ruby/ruby/exercises/concept/README.md#implemented-exercises (at 58:27) | File not found. Check if file exists and path is correct
  • [ERROR] file:///home/runner/work/ruby/ruby/exercises/concept/strings (at 74:109) | File not found. Check if file exists and path is correct

Redirects per input

Redirects in docs/24pullrequests.md
Redirects in docs/LEARNING.md

Suggestions per input

Suggestions in docs/24pullrequests.md
Suggestions in docs/LEARNING.md

Full Github Actions output

Dominant language
Ruby
Stars
597
Forks
531
Avg merge
4d 7h
Merged PRs (30d)
6

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

  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 exercism/ruby

All issues in exercism/ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.