Various problems encountered after a 4.6 -> 4.39 upgrade. about gitbucket HOT 5 OPEN

Hmm... Sorry for trouble in upgrading GitBucket. I would recommend upgrading GitBucket versions one by one if behind is very large like your situation. Of course, backup before upgrading is mandatory.

Anyway, thank you for your feedback. I will take a look at them one by one if those issues happen on the latest version.

from gitbucket.

Regarding this point,

In 4.6 when you clicked the Merge Pull Request button it would transform into a confirm button appearing in the same place, so two clicks in a row would perform a merge. In the current version the confirm button has moved to the opposite side of the screen so you must click, move the mouse, and click again--it's less convenient. What's worse, there is now a drop-down button that appears under the mouse after clicking the Merge Pull Request button and in its default state it has the label "Merge commit" which sort of looks like it's the confirm button if you're not paying close attention. This has tripped me up quite a few times and I wish it weren't this way.

• Basically, buttons that execute something should be located to the right bottom of the form
• At first, I thought "Confirm merge" button can be pulldown + button like "Comment" button, however, merge strategy is really important so I thought it's better to be an independent pulldown.

Since I'm not a UI specialist, it would be great if you can propose what it should be.

from gitbucket.

I'm not a UI specialist either, but I sometimes play one at work for lack of anything better. I think the pull down button concept would work well here, but if all you did was move the left-aligned initial Merge button the be right-aligned it would return to being a simple two-click operation without a mouse move.

E.g.

Or do both and use a combo button:

The strategy is important, but it's not something one changes every time. It's the more rare exception.

If you can't figure out something you can be happy with I'd just leave it as-is. This is something that I can get used to even if I don't think it's optimal for me.

I'll end with an aside I should have had in my original comment: it may sound like a complaint, but I actually really like gitbucket and recommend it to people constantly. It's the easiest way to go from zero-to-git-web-ui anywhere and is good enough that many people won't need anything else.

from gitbucket.

Thank you! Locating the initial "Merge pull request" button at right side looks good idea. It's align with our UI policy and minimize move of pointer.

from gitbucket.

I think pull request UI will be improved by #3417. Remaining things are regarding comments in diff view:

• The inline "reply" option exists for comments viewed in the diff view, but the same comments on the Conversation tab have no reply UI.
• If a comment is added on a line and then a force push changes the line and another comment is added to the new line, then when you view the comments from the Conversation tab the second comment chronologically is listed first, then the older one below it. This makes it look like they occurred in the opposite order.

from gitbucket.