Can't rebase and push commits that aren't mine?

[heygarrett]

If I rebase a branch on main (eg, jj rebase --branch @ --destination main), but the branch contains commits that aren't mine, I get the following error when trying to jj git push:

Error: Remote rejected the update of some refs (do you have permission to push to ["refs/heads/push-mvxwvwlxtkky"]?)

I do have permission because I can push new commits on this branch. But I've been able to reproduce this in two repos, rebasing branches that contain commits that aren't mine. Is this the expected behavior?

Edit: I should add that cloning the repo with git, doing the rebase and then git push --force-with-lease worked without issue to get around this.

[heygarrett]

I tried forking jj to reproduce this but wasn't able to reproduce. The private GitLab repos I'm working with do have some push restrictions, but what could be restricted that allows git push --force-with-lease but rejects jj git push after rebasing commits that aren't mine? 🤔

[bnjmnt4n]

Could it be related to this: #4561? Currently commits authored by others will not be re-signed if modified. Perhaps there is a GitLab push restriction enforcing signatures on all commits? Per the issue, rebasing with Git does re-sign commits authored by others with the current user's key.

[heygarrett]

Ah, yep! That seems to be the issue. Thanks!