glab might be too quick for GitLab

[maxice8]

Description

It is possible that GitLab will send wrong information telling it is not possible to merge if a merge request merge attempt is made too quick after rebasing it

Expected Behavior vs Actual Behavior

For it to merge on first try

Steps to Reproduce

1. Have a repo that only accepts rebased merge requests
2. rebase it with glab mr rebase
3. accept it with glab mr accept

Your Environment

• Version used (Run glab --version): glab version 1.12.1-95-gf6476eb (2020-12-23)
• Operating System and version: Fedora SilverBlue 33

[profclems]

Finally, what I expected to be brought up in the future!
I have been thinking of this lately. We would have to consider a specified number of retries for mr subcommands such as rebase, merge and approve 🤔

[maxice8]

I found that sleeping 6 seconds between rebase and merge fixes it in most cases on gitlab.alpinelinux.org

[clemsbot]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[clemsbot]

This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.