codebar / codebar/hugo-blog

Link Checker Report

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

Nobody has claimed this yet.

automated issue report
Dominant language
HTML
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Summary

Status Count
πŸ” Total 465
βœ… Successful 126
⏳ Timeouts 1
πŸ”€ Redirected 61
πŸ‘» Excluded 277
❓ Unknown 0
🚫 Errors 0
β›” Unsupported 0

Errors per input

Errors in content/posts/2015-year-in-review.md

Redirects per input

Redirects in content/posts/2015-year-in-review.md
Redirects in content/posts/2021-review-growing-against-all-odds.md
Redirects in content/posts/2022-things-are-on-the-up.md
Redirects in content/posts/2023-year-in-review.md
Redirects in content/posts/a-note-on-the-different-london-codebar-chapters.md
Redirects in content/posts/bath-ruby-2015.md
Redirects in content/posts/bath-ruby-2016.md
Redirects in content/posts/bournemouth-codebar.md
Redirects in content/posts/clojurebridge-london.md
Redirects in content/posts/codebar-festival-2022-wrapped.md
Redirects in content/posts/codebar-festival-2023-wrapped-the-first-hybrid-edi.md
Redirects in content/posts/community-partner-at-delta-v-conference.md
Redirects in content/posts/euruko-2015.md
Redirects in content/posts/get-to-know-a-series.md
Redirects in content/posts/introducing-codebar-festival.md
Redirects in content/posts/introducing-our-new-visual-identity.md
Redirects in content/posts/kickstart-your-development-career.md
Redirects in content/posts/london-chapters.md
Redirects in content/posts/makers-scholarship.md
Redirects in content/posts/mind-the-code.md
Redirects in content/posts/responsive-day-out-3.md
Redirects in content/posts/scotlandjs-2016.md
Redirects in content/posts/uncodebar.md
Redirects in content/posts/virtual-codebar.md
Redirects in content/posts/we-re-back-uncodebar-8.md

Full Github Actions output

Contributor guide

Open the contributing guide

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.

Research direction

Start with the reported entries in content/posts/2015-year-in-review.md and the other content/posts files listed in the report. Verify which timeout, error, and redirect results still need changes, then update the affected content links. Done means the intended links resolve without reported failures when the link checker is run again.

Written by the indexing model from the issue text.

Assessment

Tech stack
hugo
Domain
content
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.