Skip to content
Snippets Groups Projects

Merge request link displays as 404 when not logged in

    • Open Issue created by benjaoming @benjaoming

    Problem to solve

    Login sessions time out, which is more or less confusing if one is not aware that.

    When pushing to Gitlab via the terminal, it's a bit unintuitive that one's login can be expired at the same time. Here is the output from a recent push that I made:

    $ git push --set-upstream origin usb-ethernet-and-usb3-support
Counting objects: 15, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (15/15), 110.21 MiB | 1.72 MiB/s, done.
Total 15 (delta 7), reused 0 (delta 0)
remote: 
remote: To create a merge request for usb-ethernet-and-usb3-support, visit:
remote:   https://gitlab.com/fairdk/lcrs2/merge_requests/new?merge_request%5Bsource_branch%5D=usb-ethernet-and-usb3-support
remote: 
To gitlab.com:fairdk/lcrs2.git
 * [new branch]      usb-ethernet-and-usb3-support -> usb-ethernet-and-usb3-support

    Clicking the link to create a Merge Request displays a 404 page.

    The link works, when the user is logged in. But instead of the 404 page, it would be nice to be redirected to the login page.

    Intended users

    Normal users

    Further details

    Better workflow, less confusion.

    Proposal

    I'm not a Gitlab dev :)

    Permissions and Security

    Unknown

    Documentation

    Unknown

    Testing

    Unknown, maybe there are unit tests that expect 404s that should expect redirects to the login page.

    What does success look like, and how can we measure that?

    I would like to see the login page with a generic message like "To continue to the request page, please login below".

    Links / references

    Designs

      Child items ...