Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork6.3k
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
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 to53146a8Compare
wxiaoguang left a comment
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
Uh oh!
There was an error while loading.Please reload this page.
silverwind commentedJul 9, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I tested this branch, it seems to fully both issues from#34991. We should definitely backport this to 1.24. |
Uh oh!
There was an error while loading.Please reload this page.
silverwind left a comment
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.
silverwind commentedJul 10, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Actually I found the issue. In configuration I had |
wxiaoguang commentedJul 10, 2025
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. |
silverwind commentedJul 10, 2025
Yeah it's possible that the incorrect value came from that incorrect config rewrite. In any case, I'm glad we figured it out. |
silverwind commentedJul 10, 2025
@wxiaoguang is this good to merge from your side? |
wxiaoguang commentedJul 10, 2025
The code written by me surely looks good to me. So I asked other maintainers to review. |
7a15334 intogo-gitea:mainUh oh!
There was an error while loading.Please reload this page.
* 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.