[go: up one dir, main page]

Skip to content

MR rebase buttons take a long time to appear

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

This probably depends on the size of a repo, but for a large repo in a self-managed gitlab instance, it is now taking something like 15 seconds for the rebase buttons to appear. Subsequent loads are faster (so it seems to cache, at least).

Basically every time we need to go merge, because somebody else has merged beforehand, we need to sit and wait for the buttons to appear, click on them, then again sit and wait for the rebase to go through, click merge, then again wait to see if it actually went through.

The real solution, in my opinion, would be to always have a Rebase and Merge button visible (as suggested by #895). If due to some condition the rebase and merge can't work, fine fail and tell me. At least let me attempt the process. Don't force us to waste my time waiting. Perhaps worth noting that what I am suggesting is how Gerrit does this. Gitlab's approach feels like a regression.

Alternately, please improve performance to make the buttons show up faster on first load.

(yes, I'm aware of merge trains - there are reasons we don't use them in this project)

Edited by 🤖 GitLab Bot 🤖