Signpost data breach form #1775
Merged
Conversation
This file contains 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
mdeuk
reviewed
Aug 25, 2023
mdeuk
reviewed
Aug 25, 2023
|
I've added a couple of in-line comments, sorry I messed up the Git formatting a bit. As an aside, I'll raise a ticket for reconciling the same changes into This shouldn't hold up the PR here, we can follow up afterwards, since we'll need a translation. |
While it's linked from the sidebar, it might not be obvious to FOI officers navigating to the contact page (likely via the footer).
Consistency…
mysociety-pusher
force-pushed
the
signpost-data-breach-form
branch
from
8f33899
to
18b631d
Compare
|
Updates after review:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While it's linked from the sidebar, it might not be obvious to FOI officers navigating to the contact page (likely via the footer).