Skip to content

Commit f44ee68

Browse files
iirojiiroj
authored
Merge pull request #1786 from lint-staged/update-repo-url
Update repo url
2 parents a36ec1e + a61cf18 commit f44ee68

8 files changed

Lines changed: 807 additions & 832 deletions

File tree

‎.changeset/config.json‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,12 @@
11
{
22
"$schema": "https://unpkg.com/@changesets/config@2.3.1/schema.json",
3-
"changelog": ["@changesets/changelog-github", { "repo": "okonet/lint-staged" }],
3+
"changelog": [
4+
"@changesets/changelog-github",
5+
{
6+
"disableThanks": true,
7+
"repo": "lint-staged/lint-staged"
8+
}
9+
],
410
"access": "public",
511
"baseBranch": "main"
612
}

‎.changeset/famous-camels-punch.md‎

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

‎CHANGELOG.md‎

Lines changed: 586 additions & 586 deletions
Large diffs are not rendered by default.

‎README.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ See [examples](#examples) and [configuration](#configuration) for more informati
9292
9393
## Changelog
9494

95-
See [Releases](https://github.com/okonet/lint-staged/releases).
95+
See [Releases](https://github.com/lint-staged/lint-staged/releases).
9696

9797
### Migration
9898

@@ -396,7 +396,7 @@ This will result in _lint-staged_ running `eslint file-1.js file-2.js`, when you
396396

397397
## Using JS configuration files
398398

399-
Writing the configuration file in JavaScript is the most powerful way to configure lint-staged (`lint-staged.config.js`, [similar](https://github.com/okonet/lint-staged#configuration), or passed via `--config`). From the configuration file, you can export either a single function or an object.
399+
Writing the configuration file in JavaScript is the most powerful way to configure lint-staged (`lint-staged.config.js`, [similar](https://github.com/lint-staged/lint-staged#configuration), or passed via `--config`). From the configuration file, you can export either a single function or an object.
400400

401401
If the `exports` value is a function, it will receive an array of all staged filenames. You can then build your own matchers for the files and return a command string or an array of command strings. These strings are considered complete and should include the filename arguments, if wanted.
402402

@@ -497,7 +497,7 @@ export default {
497497
<details>
498498
<summary>Click to expand</summary>
499499

500-
It's better to use the [function-based configuration (seen above)](https://github.com/okonet/lint-staged#example-export-a-function-to-build-your-own-matchers), if your use case is this.
500+
It's better to use the [function-based configuration (seen above)](https://github.com/lint-staged/lint-staged#example-export-a-function-to-build-your-own-matchers), if your use case is this.
501501

502502
```js
503503
// lint-staged.config.js
@@ -945,7 +945,7 @@ tl;dr: Yes, but the pattern should start with `../`.
945945

946946
By default, `lint-staged` executes tasks only on the files present inside the project folder(where `lint-staged` is installed and run from).
947947
So this question is relevant _only_ when the project folder is a child folder inside the git repo.
948-
In certain project setups, it might be desirable to bypass this restriction. See [#425](https://github.com/okonet/lint-staged/issues/425), [#487](https://github.com/okonet/lint-staged/issues/487) for more context.
948+
In certain project setups, it might be desirable to bypass this restriction. See [#425](https://github.com/lint-staged/lint-staged/issues/425), [#487](https://github.com/lint-staged/lint-staged/issues/487) for more context.
949949

950950
`lint-staged` provides an escape hatch for the same(`>= v7.3.0`). For patterns that start with `../`, all the staged files are allowed to match against the pattern.
951951
Note that patterns like `*.js`, `**/*.js` will still only match the project files and not any of the files in parent or sibling directories.
@@ -993,7 +993,7 @@ npx lint-staged --diff="$(git merge-base main HEAD)"
993993

994994
You should not use `ng lint` through _lint-staged_, because it's designed to lint an entire project. Instead, you can add `ng lint` to your git pre-commit hook the same way as you would run lint-staged.
995995

996-
See issue [!951](https://github.com/okonet/lint-staged/issues/951) for more details and possible workarounds.
996+
See issue [!951](https://github.com/lint-staged/lint-staged/issues/951) for more details and possible workarounds.
997997

998998
</details>
999999

@@ -1033,7 +1033,7 @@ export default {
10331033

10341034
In versions of ESLint > 7, [isPathIgnored](https://eslint.org/docs/developer-guide/nodejs-api#-eslintispathignoredfilepath) is an async function and now returns a promise. The code below can be used to reinstate the above functionality.
10351035

1036-
Since [10.5.3](https://github.com/okonet/lint-staged/releases), any errors due to a bad ESLint config will come through to the console.
1036+
Since [10.5.3](https://github.com/lint-staged/lint-staged/releases), any errors due to a bad ESLint config will come through to the console.
10371037

10381038
```js
10391039
import { ESLint } from 'eslint'
@@ -1088,7 +1088,7 @@ When running `lint-staged` via Husky hooks, TypeScript may ignore `tsconfig.json
10881088
> **TS17004:** Cannot use JSX unless the '--jsx' flag is provided.
10891089
> **TS1056:** Accessors are only available when targeting ECMAScript 5 and higher.
10901090
1091-
See issue [#825](https://github.com/okonet/lint-staged/issues/825) for more details.
1091+
See issue [#825](https://github.com/lint-staged/lint-staged/issues/825) for more details.
10921092

10931093
#### Root Cause
10941094

‎lib/messages.js‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ export const invalidOption = (name, value, message) => `${red(`${error} Validati
5959
6060
${message}
6161
62-
See https://github.com/okonet/lint-staged#command-line-flags`
62+
See https://github.com/lint-staged/lint-staged#command-line-flags`
6363

6464
export const PREVENTED_EMPTY_COMMIT = `
6565
${yellow(`${warning} lint-staged prevented an empty git commit.
@@ -87,7 +87,7 @@ export const failedToParseConfig = (
8787
8888
${error}
8989
90-
See https://github.com/okonet/lint-staged#configuration.`
90+
See https://github.com/lint-staged/lint-staged#configuration.`
9191

9292
export const UNSTAGED_CHANGES_BACKUP_STASH_LOCATION = `Unstaged changes have been kept back in a patch file:`
9393

0 commit comments

Comments
 (0)