SoulSeekkor
commented
5 months ago So this might not be an issue but I'd like to verify. For these repos I also ripped out LFS, so I think that may have caused the previous commits to be marked as suspicious. Before this gets closed if that is indeed the case, is there any way of rewriting history that doesn't cause that to happen with a signed commit since the changes weren't messed with (I assume no since that's the nature of it). I'd also assume there is no way to have Gitea recognize these as valid commits either instead of suspicious?
lunny
Description
I updated my GPG key within Gitea yesterday since I had to have no expiration (since it was going to expire in a month, so I removed the expiration). Same key ID, just updated the expiration. The weirdness came when I started looking at my repos, the very last commit (which was with the old expiration) on all the repos are showing as verified but ALL of the rest of the commits after show as suspicious for some reason even though it's the same key used to sign them. Even more strange, is someone else's commits are showing as suspicious who did NOT update their GPG key.
The only other thing I've done was set up in the config a new GPG key on that server locally for use by Gitea when doing pull request merges since all repos now require signed commits. I removed that section though and it made no difference in how this page was showing up.
Gitea Version
1.21.10
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
2.42.0
Operating System
Windows Server 2019
How are you running Gitea?
Windows service.
Database
MSSQL