-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fix checks in PR for empty commits #19603 #20290
Fix checks in PR for empty commits #19603 #20290
Conversation
jedi7
commented
Jul 8, 2022
- Fixes issue Not able to merge commit in PR when branches content is same, but different commit id #19603
- fill HeadCommitID in PullRequest
- compare real commits ID as check for merging
- based on @zeripath patch in Fix merge of PR with meta/empty commit #19738
* Fixes issue go-gitea#19603 * fill HeadCommitID in PullRequest * compare real commits ID as check for merging * basd on zeripath patch
7c2d005
to
d686e09
Compare
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
OK so the problem with the initial patch is that |
is there way to restart build? Seems it was killed. |
Co-authored-by: Gusted <williamzijl7@hotmail.com>
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.
LGTM
Codecov Report
@@ Coverage Diff @@
## main #20290 +/- ##
=======================================
Coverage ? 46.94%
=======================================
Files ? 976
Lines ? 135031
Branches ? 0
=======================================
Hits ? 63390
Misses ? 63881
Partials ? 7760
Continue to review full report at Codecov.
|
Thanks. Will be possible to get it into ver 1.17 ? Or is too late? The release 1.18 will be after 6 months, right? |
I think it's fine to backport to 1.17, can you send a backport? I will vote a LGTM. |
@wxiaoguang What are proper steps please? PR against the branch release/1.17 ? |
Yup. Here is a document for reference: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#backports-and-frontports Personally I sometimes just checkout the old (1.17) branch , create a new branch for backport and cherry-pick the commit from main branch (manually). If there are not too many conflicts, it will be easy. If there are a lot of conflicts: (either) give up the backport if the backport is not important (or) fix the backport carefully if the backport is very important. |
* giteaofficial/main: Fix icon margin in user/settings/repos (go-gitea#20281) Fix org label open count, including close count issue (go-gitea#20353) [skip ci] Updated translations via Crowdin Prevent context deadline error propagation in GetCommitsInfo (go-gitea#20346) Add missing return for when topic isn't found (go-gitea#20351) Upgrade to Node 18 on CI (go-gitea#20340) Fix checks in PR for empty commits go-gitea#19603 (go-gitea#20290) Use default values when provided values are empty (go-gitea#20318) Add tests for the host checking logic, clarify the behaviors (go-gitea#20328) Changelog for 1.16.9 (update) (go-gitea#20341) (go-gitea#20343) Fix various typos (go-gitea#20338) Correctly handle draft releases without a tag (go-gitea#20314) Add write check for creating Commit status (go-gitea#20332) Remove blue text on migrate page (go-gitea#20273) Updated dead link to Madeleine.js source (go-gitea#20322)
* Fixes issue go-gitea#19603 (Not able to merge commit in PR when branches content is same, but different commit id) * fill HeadCommitID in PullRequest * compare real commits ID as check for merging * based on @zeripath patch in go-gitea#19738