#1788f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:
after editing <file> it is staged with git add <file>, and then committed with git commit
after editing <file> it is committed with git commit --all without explicit git add
after editing <file> it is committed with git commit <pathspec> without explicit git add
There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.
<h1>npm</h1>
<h2>lint-staged</h2>
<ul>
<li> ^17.0.3 => ^17.0.4 (vscodestat)</li>
</ul>
> <h3>Patch Changes</h3>
> <ul>
> <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1788">#1788</a> <a href="https://github.com/lint-staged/lint-staged/commit/f95c1f8df3368758c44c2052e568aac1b3d4c767"><code>f95c1f8</code></a> - Another fix for making sure <em>lint-staged</em> adds task modifications correctly to the commit in the following cases:</p>
> <ul>
> <li>after editing <code><file></code> it is staged with <code>git add <file></code>, and then committed with <code>git commit</code></li>
> <li>after editing <code><file></code> it is committed with <code>git commit --all</code> without explicit <code>git add</code></li>
> <li>after editing <code><file></code> it is committed with <code>git commit <pathspec></code> without explicit <code>git add</code></li>
> </ul>
> <p>There's new test cases which actually setup the Git <code>pre_commit</code> hook to run <em>lint-staged</em> and verify them. These issues started in <strong>v17.0.0</strong> when trying to improve support for committig without having explicitly staged files.</p>
> </li>
> </ul>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
npm
lint-staged