How to determine if a rebase is needed for an MR #2006
Replies: 2 comments 1 reply
-
Has the project been set to require only fast-forward merge? If so then the status should not be Also there is I look at the following: A merge request should be rebased if it meets the following conditions:
|
Beta Was this translation helpful? Give feedback.
-
Hi @FirefighterBlu3, I think you're looking for the Otherwise, this largely depends on whether the information is available from the API. These statuses are calculated by the server asynchronously (https://docs.gitlab.com/ee/api/merge_requests.html#single-merge-request-response-notes), so you'd need to continuously poll to get the right status. I suggest you look through the upstream docs for hints. If this information is not available from the server, then unfortunately there isn't much python-gitlab can do as it just wraps the API calls. |
Beta Was this translation helpful? Give feedback.
-
After an MR is created, how do we:
example messages:
please note that mr.merge_status == 'can_be_merged' and mr.has_conflicts == False
Beta Was this translation helpful? Give feedback.
All reactions