-
-
Notifications
You must be signed in to change notification settings - Fork 6k
Comparing changes
Open a pull request
base repository: go-gitea/gitea
base: v1.18.4
head repository: go-gitea/gitea
compare: v1.18.5
- 9 commits
- 34 files changed
- 11 contributors
Commits on Feb 21, 2023
-
Hide 2FA status from other members in organization members list (#22999…
Configuration menu - View commit details
-
Copy full SHA for 660a83b - Browse repository at this point
Copy the full SHA 660a83bView commit details -
Use
--message=%s
for git commit message (#23028) (#23029)Backport #23028 This backport is done by manually because the git module is different.
Configuration menu - View commit details
-
Copy full SHA for c50d420 - Browse repository at this point
Copy the full SHA c50d420View commit details -
Fix the Manually Merged form (#23015) (#23017)
Backport #23015 --------- Co-authored-by: Jason Song <i@wolfogre.com>
Configuration menu - View commit details
-
Copy full SHA for 7b3ffe5 - Browse repository at this point
Copy the full SHA 7b3ffe5View commit details -
Render access log template as text instead of HTML (#23013) (#23025)
Backport #23013 Fix #22906 (comment) Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 8fa62be - Browse repository at this point
Copy the full SHA 8fa62beView commit details -
Add force_merge to merge request and fix checking mergable (#23010) (#…
…23032) Backport #23010. Fix #23000. The bug was introduced in #22633, and it seems that it has been noticed: #22633 (comment) . However, #22633 did nothing wrong, the logic should be "check if they is admin only when `force` is true". So we should provide the `ForceMerge` when merging from UI. After this, an admin can also send a normal merge request with `ForceMerge` false. So it fixes a potential bug: if the admin doesn't want to do a force merge, they just see the green "Merge" button and click it. At the same time, the status of the PR changed, and it shouldn't be merged now, so the admin could send an unexpected force merge. In addition, I updated `ForceMerge *bool` to `ForceMerge bool`, I don't see the reason to use a pointer. And fixed the logic of CheckPullMergable to handle auto merge and force merge correctly.
Configuration menu - View commit details
-
Copy full SHA for 90982bf - Browse repository at this point
Copy the full SHA 90982bfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 760cf41 - Browse repository at this point
Copy the full SHA 760cf41View commit details -
Display attachments of review comment when comment content is blank (#…
Configuration menu - View commit details
-
Copy full SHA for bbfd345 - Browse repository at this point
Copy the full SHA bbfd345View commit details -
Return empty url for submodule tree entries (#23043) (#23048)
Backport #23043 Close #22614. Refer to [Github's API](https://docs.github.com/en/rest/git/trees?apiVersion=2022-11-28#get-a-tree), if a tree entry is a submodule, its url will be an empty string. Co-authored-by: Zettat123 <zettat123@gmail.com> Co-authored-by: delvh <leon@kske.dev> Co-authored-by: John Olheiser <john.olheiser@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 8f5b2f1 - Browse repository at this point
Copy the full SHA 8f5b2f1View commit details -
Signed-off-by: jolheiser <john.olheiser@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 48eb5ac - Browse repository at this point
Copy the full SHA 48eb5acView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.18.4...v1.18.5