-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add note to GPG key response if user has no keys #18961
Conversation
Yes.
So far I can see, it's only used in the web part. |
Yes, but the response looks like something a tool uses as input which could be confused by html error page. |
Well, I hope that tools can detect a simple 404 statuscode 😅 . |
This response should be:
|
CI errors are related |
Should this be backported? |
This is very minor - a backport is reasonable but equally not sending one is also reasonable. |
* giteaofficial/main: Don't clean up hardcoded `tmp` (go-gitea#18983) git backend ignore replace objects (go-gitea#18979) Improve the deletion of issue (go-gitea#18945) Add note to GPG key response if user has no keys (go-gitea#18961) adds restore docs for docker based instances (go-gitea#18844) Refactor admin user filter query parameters (go-gitea#18965)
* main: ignore missing comment for user notifications (go-gitea#18954) allow overwrite artifacts for github releases (go-gitea#18987) fix & refactor (go-gitea#18973) Don't clean up hardcoded `tmp` (go-gitea#18983) git backend ignore replace objects (go-gitea#18979) Improve the deletion of issue (go-gitea#18945) Add note to GPG key response if user has no keys (go-gitea#18961) adds restore docs for docker based instances (go-gitea#18844) Refactor admin user filter query parameters (go-gitea#18965)
* Prevent invalid key response. * Display note instead of 404 response. * Fixed test. Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Prevents the invalid reponse if there are no keys:Additional questions:ShouldShowSSHKeys
do the same?Is this an "api" endpoint and the response should be just the plain 404 response code instead of the html page? If yes we need to add an addition route for/orgs/<org>.gpg
to get the same behaviour there too.Adds a note if user has no keys.