Checking for broken links with TravisCI
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 48/100
Research direction
Start by checking the repository's .travis.yml and the status of issue #19, which is identified as a prerequisite. Compare the existing CI configuration with the proposed Jekyll build and htmlproof commands; done means TravisCI checks generated links and reports bad or broken links in pull requests.
Written by the indexing model from the issue text.
Description
See #19 for fixing all the existing broken links.
Once that's done, we should add a link checker to TravisCI to keep appraised of any broken links (due to external site changes) or bad links in incoming pull request.
@JoaoRodrigues suggested following https://www.jacobtomlinson.co.uk/jekyll/2015/02/18/test-you-jekyll-blog-with-travis-ci/ which suggests this for the .travis.yml file:
language: ruby
rvm:
- 2.1
script:
- bundle exec jekyll build
- bundle exec htmlproof ./_site --only-4xx --check-favicon --check-html
env:
global:
- NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer
- Dominant language
- CSS
- Stars
- 167
- Forks
- 379
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 biopython/biopython.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
biopython/biopython.github.io#117 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
biopython/biopython.github.io#98 · 3 comments ·
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 42/100
biopython/biopython.github.io#85 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
biopython/biopython.github.io#84 · 8 comments ·
-
Include build instructions in README so contributors can (easily) get a local Jekyll setup going Openhelp wanted
Difficulty 2/5 Half a day Newbie friendliness 42/100
biopython/biopython.github.io#79 · 6 comments ·
All issues in biopython/biopython.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NVIDIA/gpu-operator#2955 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
automated issue report
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dsx-ai-factory/infra-controller#6694 ·
-
bug build
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
facebookincubator/velox#19143 ·