<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=415400) </details> <!--IssueSummary end--> I spent several minutes trying to add a push mirror in the Repository settings. Things I did wrong: 1. Left out `.git` in the URL. This resulted in a 301 error (https://forum.gitlab.com/t/fork-synching-by-using-mirroring-repositories-fails/32235/2). 2. Added a username and password to the URL (e.g. https://user:mypassword@gitlab.example.com), expecting the password to be extracted. Left the password out in the form. Turns out that doesn't work. 3. Not being sure about `username:password` syntax. It might be clearer if we add a separate `Username` field that also gets populated if a user enters this in the URL. I'd suggest: 1. Warn or automatically append `.git` for well-known providers. Or allow redirects to `.git`. 2. Automatically extract the password if it's not provided in the form. This could be done on the backend and/or frontend (the latter would at least provide feedback to the user). 3. Make it possible to edit the settings with a new username/password or URL. 4. Add a `username` field. Also the alignment seems off: