Include visible hints on actions that would trigger a merge with auto-merge/MWCP
Release notes
Problem to solve
As a reviewer, I don't generally keep track of which checks are actually still blocking a merge. For example, if I'm just responding to a comment on an open discussion and happen to resolve the thread, then it might come as a surprise if the MR gets merged. This can be a problem for projects like gitlab-org/gitlab
, that:
- use merged results pipelines but not merge trains,
- ask that latest pipeline be relatively recent prior to merging
- rely on maintainers to start pipelines based on their own judgement (we have a 4 hour suggested maximum age)
Proposal
Make it clear when an particular action would result in a merge, so that the user can act accordingly.
Intended users
Feature Usage Metrics
Does this feature require an audit event?
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.