Marc Bernard

the default for `config.web.login` is true. The if-statement is wrong https://github.com/verdaccio/verdaccio/blob/96d2f0f24d42c2ad1613902178243d48024bdc1b/packages/web/src/api/package.ts#L26C2-L26C54 It should use this instead: https://github.com/verdaccio/verdaccio/blob/96d2f0f24d42c2ad1613902178243d48024bdc1b/packages/web/src/web-utils.ts#L5-L7 Fix for master (#5280) and 6.x (#5279)

@abdelfattahradwan since it doesn't work with `config.web.login = true` for you, my fix won't solve your issue. Please open a new issue where we can dig into details. Attach the...

No need to reopen. See https://github.com/verdaccio/verdaccio/issues/5281#issuecomment-2995854894

In git terms, it's a +2, -1 since there's no "change" in git diff. You get a yellow "change" in abapGit if there's a + or - on both sides...

I would be ok with just red/green as the default, if - there's a switch in the view menu to also show yellow (current behaviour) - we persist the view...

For a good 2 hours, I could not figure out why the new tests were failing. AI could not figure it out either! Somehow, we finally saw that there was...

I rebased all my PRs. This one contained a doc update which I will do as a follow up.

I'm mostly on A4H 1909 (in process of moving to 2023SP1) and haven't seen this issue. There certainly were changes like https://github.com/abapGit/abapGit/pull/7176. But they just impact how the parallel degree...

This is a tricky one. A limitation of abapGit. We keep only one set of checksums (for the current branch). When you switch branches, the checksums might not be correct...

In your case, remote should not be ahead (more commits on remote than local). So updating the checksum should result in detecting local changes which can be pushed to remote.