the problem: we get to a 404 page if not signed in and trying to access a private repository from its link.
possible solution:
best: recognize it is an access problem and ask user to sign in
workaround: Modify the 404 page to include the user may need to sign in first, and give a link to the login button (absent now)
the problem: we get to a 404 page if not signed in and trying to access a private repository from its link.
possible solution:
best: recognize it is an access problem and ask user to sign in
workaround: Modify the 404 page to include the user may need to sign in first, and give a link to the login button (absent now)
Hi Julien. This isn't a bad idea. We would need different 404 pages for when users are logged in or not (we don't want to be telling logged in users to log in), so I'll have to think about some of the details.
Thanks for the suggestion.
Hi Julien. This isn't a bad idea. We would need different 404 pages for when users are logged in or not (we don't want to be telling logged in users to log in), so I'll have to think about some of the details.
Thanks for the suggestion.
the problem: we get to a 404 page if not signed in and trying to access a private repository from its link.
possible solution: best: recognize it is an access problem and ask user to sign in workaround: Modify the 404 page to include the user may need to sign in first, and give a link to the login button (absent now)
Hi Julien. This isn't a bad idea. We would need different 404 pages for when users are logged in or not (we don't want to be telling logged in users to log in), so I'll have to think about some of the details.
Thanks for the suggestion.