Skip to content

Commit 69840cc

Browse files
refactor: update outdated ESLint and OpenJS links (#322)
* chore: update outdated ESLint and OpenJS links * refactor: use openjsf.org/cla instead of cla.openjsf.org Co-authored-by: lumir <yonghyeon0324@gmail.com> --------- Co-authored-by: lumir <yonghyeon0324@gmail.com>
1 parent 89db694 commit 69840cc

4 files changed

Lines changed: 113 additions & 113 deletions

File tree

CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Please be sure to read the contribution guidelines before making or requesting a
44

55
## Code of Conduct
66

7-
This project adheres to the [JS Foundation Code of Conduct](https://js.foundation/community/code-of-conduct). We kindly request that you read over our code of conduct before contributing.
7+
This project adheres to the [OpenJS Foundation Code of Conduct](https://eslint.org/conduct). We kindly request that you read over our code of conduct before contributing.
88

99
## Filing Issues
1010

@@ -16,4 +16,4 @@ This project adheres to the [JS Foundation Code of Conduct](https://js.foundatio
1616

1717
## Contributing Code
1818

19-
Please sign our [Contributor License Agreement](https://cla.js.foundation/eslint/eslint) and read over the [Pull Request Guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests).
19+
Please sign our [Contributor License Agreement](https://openjsf.org/cla) and read over the [Pull Request Guidelines](https://eslint.org/docs/latest/contribute/pull-requests).

docs/commit-message-check.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22

33
## Background
44

5-
`eslint-github-bot`'s commit message check ensures that all pull requests which get merged into `main` have a valid commit message, based on [ESLint's commit message guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes).
5+
`eslint-github-bot`'s commit message check ensures that all pull requests which get merged into `main` have a valid commit message, based on [ESLint's commit message guidelines](https://eslint.org/docs/latest/contribute/pull-requests#step-2-make-your-changes).
66

77
The ESLint team uses GitHub's "Squash and Merge" feature to merge pull requests. When using this feature, the default commit message for the squashed commit is the title of the pull request. To minimize the risk of an incorrect commit message getting merged into `main`, `eslint-github-bot` checks the title.
88

99
## How do I fix it?
1010

11-
If this status check is failing on your pull request, you should fix your pull request title on github.com to conform to [ESLint's commit message guidelines](https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes).
11+
If this status check is failing on your pull request, you should fix your pull request title on github.com to conform to [ESLint's commit message guidelines](https://eslint.org/docs/latest/contribute/pull-requests#step-2-make-your-changes).
1212

1313
![](./edit-pr-title-explanation.png)

src/plugins/commit-message/createMessage.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,6 @@ ${errorMessages.join("\n")}
4141
4242
**To Fix:** You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.
4343
44-
Read more about contributing to ESLint [here](https://eslint.org/docs/developer-guide/contributing/)
44+
Read more about contributing to ESLint [here](https://eslint.org/docs/latest/contribute/)
4545
`;
4646
};

0 commit comments

Comments
 (0)