Can you split the commit in two (first commit the tests, after that commit the fix) so that we can see the red CI first? This way it's pure TDD style, you know.

Can you split the commit in two (first commit the tests, after that commit the fix) so that we can see the red CI first? This way it's pure TDD style, you know.

you want it red in CI or is it okay to commit with test.fails -> test?

I think two commits are good, one fails CI, one makes it green. Does this work?

to commit with test.fails -> test?

Sorry I don't know what you mean with this.

BTW I just saw that you did a single push with 2 commits. The point is do a push per commit.
You can do this with git using this kind of command: https://stackoverflow.com/a/45155607/23158491

Or if you want a script, I developed one:
https://github.com/tarsgate/conventions/blob/master/scripts/gitPush1by1.fsx

Although, not sure if you have to wait first for @escapedcat to approve the workflows

Try this:

1. fix format issues
2. create a commit that fails CI
3. fix code
4. create a commit that passes CI
5. tackle copilot feedback

Try this:
fix format issues

But bro, you're the one that broke the formatting in master 😆

to commit with test.fails -> test?

Sorry I don't know what you mean with this.

What I did was two commits:

1. assert the tests fail
2. commit fix and change the tests to assert success

BTW I just saw that you did a single push with 2 commits. The point is do a push per commit.
Okay, sure I can do it like that

Try this:
fix format issues

But bro, you're the one that broke the formatting in master 😆

Fixed: #4768

First commit
d75f703 (test: add tests for missing coverage, 2026-05-14)
fails the tests, like you asked @knocte

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  @commitlint/read/src/read.test.ts > throws when from and to share no merge-base
AssertionError: promise resolved "[ 'orphan commit\n\n' ]" instead of rejecting

- Expected:
Error {
  "message": "rejected promise",
}

+ Received:
[
  "orphan commit

",
]

 ❯ @commitlint/read/src/read.test.ts:170:62
    168|  });
    169|
    170|  await expect(read({ from: initialBranch, to: "other", cwd })).rejects.toThrow(
       |                                                              ^
    171|   /Cannot find merge-base/,
    172|  );

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯

 FAIL  @commitlint/read/src/read.test.ts > throws when from has no merge-base with HEAD (no --to)
AssertionError: promise resolved "[ 'orphan commit\n\n' ]" instead of rejecting

- Expected:
Error {
  "message": "rejected promise",
}

+ Received:
[
  "orphan commit

",
]

 ❯ @commitlint/read/src/read.test.ts:191:49
    189|  });
    190|
    191|  await expect(read({ from: initialBranch, cwd })).rejects.toThrow(
       |                                                 ^
    192|   /Cannot find merge-base/,
    193|  );

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯


 Test Files  1 failed | 89 passed (90)
      Tests  2 failed | 1188 passed (1190)
Type Errors  no errors
   Start at  12:48:46
   Duration  24.71s (transform 4.25s, setup 0ms, import 12.65s, tests 54.74s, environment 1.32s, typecheck 499ms)

error Command failed with exit code 1.

btw, the current vitest.config.ts doesn't play nice with vim undo/swap files. Maybe consider excluding hidden files or tightening the include smh

diff --git a/vitest.config.ts b/vitest.config.ts
index 09b59699..0d9f802d 100644
--- a/vitest.config.ts
+++ b/vitest.config.ts
@@ -15,6 +15,7 @@ export default defineConfig({
                coverage: {
                        provider: "istanbul",
                        include: ["**/@commitlint/*/src/**"],
+                       exclude: ["**/.*"],
                },
        },
        environments: {

rebased and re-formatted

fails the tests, like you asked @knocte

You still pushed both commits with the same push operation, so we only see one CI status.

fails the tests, like you asked @knocte

You still pushed both commits with the same push operation, so we only see one CI status.

Earlier I pushed them separetly

I will re force-push the first commit
how long do I need to wait before pushing the full series for CI to register in a way which shows the red CI like you want?

how long do I need to wait

No need to wait IME. However, I see what's happening here: everytime you push, @escapedcat needs to approve the CI workflow run. So I'm afraid you have to push 1st commit first, then wait until he approves, and then push again.

Looks good! I see broken CI now, then you can now push 2nd commit.

Looks good, thanks! undraft?

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

Thanks everybody! ❤️