You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't fully support protected branches everywhere in the UI, but we should handle better a few cases since renku-core actually supports that case.
Currently, updating a project with protected branches using the "Update" button from the settings page seems to work but actually leaves the user with the same update button.
Proposal
When migrating a project with a protected branch, we should show a warning and a link to a merge request on GitLab.
This should be easy since renku-core return an ad-hoc response in that case containing the field remote_branch.
Motivation
We don't fully support protected branches everywhere in the UI, but we should handle better a few cases since renku-core actually supports that case.
Currently, updating a project with protected branches using the "Update" button from the settings page seems to work but actually leaves the user with the same update button.
Proposal
When migrating a project with a protected branch, we should show a warning and a link to a merge request on GitLab.
This should be easy since renku-core return an ad-hoc response in that case containing the field
remote_branch
.The text was updated successfully, but these errors were encountered: