-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Fix git commit committer parsing and add some tests #35007
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
9a39900
to
53146a8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done from my side
I tested this branch, it seems to fully both issues from #34991. We should definitely backport this to 1.24. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT from functional perspective.
Actually I found the issue. In configuration I had |
Yep, this is my fourth time to fix the regressions from #33528, so I am pretty sure it is the cause. I think I also know why your "noreply address" is incorrect, I guess in old days, Gitea used the DOMAIN as noreply address, then it caused problem, then the behavior was changed (a prefix as added). BUT, in old Gitea, Gitea also had another wrong behavior: it wrote garbage config options into the config file (I also fixed that), so very old users might be affected by incorrect config options. |
Yeah it's possible that the incorrect value came from that incorrect config rewrite. In any case, I'm glad we figured it out. |
@wxiaoguang is this good to merge from your side? |
The code written by me surely looks good to me. So I asked other maintainers to review. |
* giteaofficial/main: Fix updating user visibility (go-gitea#35036) Fix git commit committer parsing and add some tests (go-gitea#35007) Refactor OpenIDConnect to support SSH/FullName sync (go-gitea#34978) Support base64-encoded agit push options (go-gitea#35037) Also display "recently pushed branch" alert on PR view (go-gitea#35001) Make submodule link work with relative path (go-gitea#35034) Update to go 1.24.5 (go-gitea#35031) Improve CLI commands (go-gitea#34973) Tweak eslint config, fix new issues (go-gitea#35019) # Conflicts: # templates/repo/commits_list.tmpl
Uh oh!
There was an error while loading. Please reload this page.