prettier permission denied - #767
Merged
Merged
Conversation
simonLeary42
force-pushed
the
prettier-permission-denied
branch
from
August 25, 2026 13:34
8bae772 to
b6a6637
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pi.phpsends "bad request" when the user is not a PI when it should be sending "forbidden".I considered making "permission denied" send a message and make the browser redirect back to home, but this seems unnecessarily confusing to the user. If they click a link and get permission denied and get teleported back to the home page, they don't even know what page was it that they got permission denied from. Instead let them see the "permission denied" message on the correct page, and provide them a hyperlink to the home page.