Still a transient bug in rebase feature
- Zendesk ticket: https://gitlab.zendesk.com/agent/tickets/9412
- Dev link: None
- GitLab version: 8.1
Expected behavior
Anytime a 'Rebase on ' button is present a rebase is expected to be required for a FF merge to be possible.
Observed behavior
Under certain circumstances (unfortunately, it's been really difficult for us to reproduce) GitLab shows the 'Rebase on ' button when a rebase is not necessary. We know this is true because we can perform a FF merge via the command line and it works fine. Clicking the rebase button in the web UI performs a rebase and we see the new commits get pushed. However, once the rebase is done it immediately shows that a rebase is necessary again.
The Zendesk ticket has a link to a GitLab.com private repository that exhibits this behavior. We have permission to access and use this repository for testing and reproduction. The developer who works this bug can ping me or @patricio for a description of what's going on and what we've tried.
Next steps
@vsizov Do you have any ideas on this? Please let us know if you need access to this private repo and how we can help. See the zendesk ticket for an in-depth history.