From d76a0ed3a8849b59292ea4006468e57782c54345 Mon Sep 17 00:00:00 2001 From: Peter Dave Hello Date: Wed, 15 Jun 2022 16:08:41 +0800 Subject: [PATCH 1/2] docs: Update GitHub links in CONTRIBUTING.md Those links in the doc are now all 301 redirected to somewhere else, should better update them before it's dead. --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6952d3789..5e1e87158 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,12 +14,12 @@ New **NPM** releases are not tracked. We simply use the NPM version bundled in t If you'd like to help us by submitting a PR for a version update, please do the following: -1. [Fork this project.](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) -1. [Clone the forked repository.](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) +1. [Fork this project.](https://docs.github.com/en/get-started/quickstart/fork-a-repo) +1. [Clone the forked repository.](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) 1. Create a branch for the update PR. For example, `git checkout main; git checkout -b version-update`. 1. Run `./update.sh`. You can see additional options by using accessing the built-in help documentation with `./update.sh -h`. This script will automatically update the appropriate files with the latest versions and checksums. 1. Commit the modified files to the `version-update` branch and push the branch to your fork. -1. [Create a PR to merge the branch from your fork into this project's default branch.](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork). +1. [Create a PR to merge the branch from your fork into this project's default branch.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork). ## Adding dependencies to the base images From 07c284ebe50708eb0c1b08872fd8e1701c099485 Mon Sep 17 00:00:00 2001 From: Peter Dave Hello Date: Thu, 16 Jun 2022 17:33:47 +0800 Subject: [PATCH 2/2] docs: Improve markdown format in README.md There should be a blank line after the headings --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 6446f33e4..c6ddbcae0 100644 --- a/README.md +++ b/README.md @@ -193,11 +193,13 @@ image as a base, add the things you need in your own Dockerfile examples of how to install packages if you are unfamiliar). ### `node:buster` + This image is based on version 10 of [Debian](http://debian.org), available in [the `debian` official image](https://hub.docker.com/_/debian). ### `node:stretch` + This image is based on version 9 of [Debian](http://debian.org), available in [the `debian` official image](https://hub.docker.com/_/debian).