Consider accepting SSL insecurity warnings for linkchecks

Open Beginner friendly
#271 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
70/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd

Research direction

Open .github/workflows/ci-linkchecks.yml at the linked line 39 and review how the link-checking workflow handles SSL warnings. Compare its behavior with the ncdata issue example, then adjust the link-checking tolerance without changing unrelated upload or download behavior. Run the link-check workflow and confirm that documentation links with SSL insecurity warnings no longer create unnecessary noise.

Written by the indexing model from the issue text.

Description

Here is one example:

For link checking, we're only talking about info/docs, we're not talking about downloading/uploading/etc. The better compromise would be to reduce the noisiness of the link checking by being more tolerant. Here is the line to change:

https://github.com/SciTools/.github/blob/575c89070eafc416b2de8ea09c58411b929ddbce/templates/github/workflows/ci-linkchecks.yml#L39

Dominant language
Python
Stars
3
Forks
7
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/.github

All issues in SciTools/.github

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.