Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable markdown-link-check #2

Merged
merged 2 commits into from Jan 15, 2023
Merged

Enable markdown-link-check #2

merged 2 commits into from Jan 15, 2023

Conversation

EliahKagan
Copy link
Owner

I'm getting 503 errors I shouldn't be, and switching from v1 to the 1.0.14 release candidate fixed that for me in another repository. Details in:

EliahKagan/userstyles#1

(Though the 503 link in this repo is to a different site.)
@EliahKagan EliahKagan merged commit 67a372d into master Jan 15, 2023
@EliahKagan EliahKagan deleted the markdown-links branch January 15, 2023 01:11
EliahKagan added a commit to EliahKagan/fps that referenced this pull request Jan 15, 2023
To fix HTTP 503 errors I shouldn't be getting.

This change fixed it in two other repos:

- EliahKagan/userstyles#1
- EliahKagan/muntineer#2
EliahKagan added a commit to EliahKagan/Flood that referenced this pull request Jan 15, 2023
To fix HTTP 503 errors I shouldn't be getting.

This change fixed it in three other repos:

- EliahKagan/userstyles#1
- EliahKagan/muntineer#2
- EliahKagan/fps#1
EliahKagan added a commit to EliahKagan/Flood that referenced this pull request Jan 15, 2023
* Enable markdown-link-check

https://github.com/marketplace/actions/markdown-link-check

* Use markdown-link-check 1.0.14

To fix HTTP 503 errors I shouldn't be getting.

This change fixed it in three other repos:

- EliahKagan/userstyles#1
- EliahKagan/muntineer#2
- EliahKagan/fps#1

* Fix typo in referenced version tag name

* Try markdown-link-check 1.0.13

Moving from v1 to 1.0.14 fixed the wrong 503 errors, but gave many new errors for hash links (links to specific sections).

It's probably gaurav-nelson/github-action-markdown-link-check#127, in which case switching to 1.0.13 won't fix the hash link problem, but I want to try that before attempting to fix both problems at once by specifying branches or untagged commits.

* Try tip of master

For markdown-link-check.

* Back to v1

* Work around fussy links
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant