#182516b3f74 - It is now possible to run multiple tasks in parallel for a single glob by configuring it with an array of tasks (which run sequentially), and then placing another array inside it (where the tasks will run in parallel). The following demonstrates the order tasks will start in:
additionally, if any *.ts files are staged, run tsc without appending any arguments
The two sets of commands also run in parallel
Patch Changes
#182915f7e53 - During an in-progress merge, files that are unchanged from the branch being merged are now skipped. Technically, files are only included if there are staged changes against both HEAD and MERGE_HEAD.
<h1>npm</h1>
<h2>lint-staged</h2>
<ul>
<li> ^17.2.0 => ^17.3.0 (vscodestat)</li>
</ul>
> <h3>Minor Changes</h3>
> <ul>
> <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1825">#1825</a> <a href="https://github.com/lint-staged/lint-staged/commit/16b3f74850e5d2811b5fbaea6c136733a71ad3e4"><code>16b3f74</code></a> - It is now possible to run multiple tasks in parallel for a single glob by configuring it with an array of tasks (which run sequentially), and then placing another array inside it (where the tasks will run in parallel). The following demonstrates the order tasks will start in:</p>
> <pre><code class="language-json">{
> "*.ts": ["first", "second", ["third", "third"], "fourth"]
> }
> </code></pre>
> <p>As a concrete example, <em>lint-staged</em>'s own configuration is:</p>
> <pre><code class="language-js">/** @type {import('./lib/index.js').Configuration} */
> export default {
> "*": [
> [
> "oxfmt --check --no-error-on-unmatched-pattern",
> "oxlint --no-error-on-unmatched-pattern",
> ],
> ],
> "*.ts": () => "tsc",
> };
> </code></pre>
> <p>which means:</p>
> <ol>
> <li>for all staged files, run the two commands in parallel with staged filenames appended, for example:<ul>
> <li><code>oxfmt --check --no-error-on-unmatched-pattern lib/index.js</code></li>
> <li><code>oxlint --no-error-on-unmatched-pattern lib/index.js</code></li>
> </ul>
> </li>
> <li>additionally, if any <code>*.ts</code> files are staged, run <code>tsc</code> without appending any arguments</li>
> <li>The two sets of commands also run in parallel</li>
> </ol>
> </li>
> </ul>
> <h3>Patch Changes</h3>
> <ul>
> <li><a href="https://github.com/lint-staged/lint-staged/pull/1829">#1829</a> <a href="https://github.com/lint-staged/lint-staged/commit/15f7e5314b4afe4702808d978758b22d42437f43"><code>15f7e53</code></a> - During an in-progress merge, files that are unchanged from the branch being merged are now skipped. Technically, files are only included if there are staged changes against both <code>HEAD</code> and <code>MERGE_HEAD</code>.</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