Checking links in markdown files (#150)

pull/151/head^2
Marco Ieni 3 years ago committed by GitHub
parent 991ab68d12
commit d7026aa694
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -0,0 +1,7 @@
{
"ignorePatterns": [
{
"pattern": "^(http|https)://crates.io/"
}
]
}

@ -0,0 +1,18 @@
name: Check Markdown links
on:
push:
branches: [master]
pull_request:
jobs:
markdown-link-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@master
- uses: gaurav-nelson/github-action-markdown-link-check@v1
with:
use-verbose-mode: 'yes'
use-quiet-mode: 'yes'
config-file: '.github/workflows/url-check-config.json'
check-modified-files-only: 'yes'

@ -0,0 +1,17 @@
name: Check Markdown links Periodically
on:
schedule:
# Run everyday at 0:00 AM
- cron: "0 0 * * *"
jobs:
markdown-link-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@master
- uses: gaurav-nelson/github-action-markdown-link-check@v1
with:
use-verbose-mode: 'yes'
use-quiet-mode: 'yes'
config-file: '.github/workflows/url-check-config.json'

@ -2,11 +2,11 @@
Refactoring is very important in relation to these topics. Just as important as the other topics covered here, is how to take good code and turn it into great code.
We can use [design patterns](patterns/index.md) to DRY up code and generalize abstractions. We must avoid [anti-patterns](anti_patterns/index.md) while we do this. While they may be tempting to employ, their costs outweigh their benefits.
We can use [design patterns](../patterns/index.md) to DRY up code and generalize abstractions. We must avoid [anti-patterns](../anti_patterns/index.md) while we do this. While they may be tempting to employ, their costs outweigh their benefits.
> Shortcuts make for long days.
We can also use [idioms](idioms/index.md) to structure our code in a way that is understandable.
We can also use [idioms](../idioms/index.md) to structure our code in a way that is understandable.
## Tests

Loading…
Cancel
Save