Skip to content

Commit c066861

Browse files
committed
ci: fix cannot validate links
1 parent 6cb303f commit c066861

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

.circleci/config.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ version: 2.1
22
jobs:
33
build:
44
docker:
5-
- image: 'cimg/node:18.12'
5+
- image: 'cimg/node:18.17'
66
steps:
77
- 'checkout'
88
# require `sudo`: https://github.com/CircleCI-Public/cimg-node/issues/277

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ a cli tool to build and sync \*ignore files across files and repositories
44

55
## Why
66

7-
1. Github default `.gitignore` doesn't cover all our needs, we always need to compose and manage multiple `.gitignore` files from github, such as [Node.gitignore](https://github.com/github/gitignore/blob/master/Node.gitignore) + [macOS.gitignore](https://github.com/github/gitignore/blob/master/Global/macOS.gitignore), in order to remove all the noises in our development. It should be automated.
7+
1. Github default `.gitignore` doesn't cover all our needs, we always need to compose and manage multiple `.gitignore` files from github, such as [Node.gitignore](https://github.com/github/gitignore/blob/main/Node.gitignore) + [macOS.gitignore](https://github.com/github/gitignore/blob/main/Global/macOS.gitignore), in order to remove all the noises in our development. It should be automated.
88

99
1. For library developer, we often need to compose a `.npmignore` from `.gitignore` and some extra ignore patterns that we do not wish to ignore by `.gitignore`, such as test files and `.*rc` files. If `.gitignore` is updated, you will need to update corresponding part of `.npmignore` manually. We should avoid this repetitive work.
1010

0 commit comments

Comments
 (0)