BigW Consortium Gitlab
When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
administration | Loading commit data... | |
api | Loading commit data... | |
ci | Loading commit data... | |
container_registry | Loading commit data... | |
customization | Loading commit data... | |
development | Loading commit data... | |
downgrade_ee_to_ce | Loading commit data... | |
gitlab-basics | Loading commit data... | |
hooks | Loading commit data... | |
incoming_email | Loading commit data... | |
install | Loading commit data... | |
integration | Loading commit data... | |
intro | Loading commit data... | |
legal | Loading commit data... | |
logs | Loading commit data... | |
markdown | Loading commit data... | |
migrate_ci_to_ce | Loading commit data... | |
monitoring | Loading commit data... | |
operations | Loading commit data... | |
permissions | Loading commit data... | |
profile | Loading commit data... | |
project_services | Loading commit data... | |
public_access | Loading commit data... | |
raketasks | Loading commit data... | |
security | Loading commit data... | |
ssh | Loading commit data... | |
system_hooks | Loading commit data... | |
university | Loading commit data... | |
update | Loading commit data... | |
user | Loading commit data... | |
web_hooks | Loading commit data... | |
workflow | Loading commit data... | |
README.md | Loading commit data... |