-
Notifications
You must be signed in to change notification settings - Fork 652
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
image-layout: use a made-up name/email for author #525
Conversation
The image spec shouldn't reference real names/addresses in example content. Switch to the same fake one we use elsewhere. It's like alternative facts. Signed-off-by: Jonathan Boulle <[email protected]>
@@ -132,7 +132,7 @@ $ cat ./blobs/sha256/afff3924849e458c5ef237db5f89539274d5e609db5db935ed3959c90f1 | |||
$ cat ./blobs/sha256/5b0bcabd1ed22e9fb1310cf6c2dec7cdef19f0ad69efa1f392e94a4333501270 | jq |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably want to update this hash to match whatever the canonical form of the new JSON is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JSON is truncated, so I'm not going to do that. Just pretend that whatever is below the ellipses ends up causing a hash collision.
1 similar comment
@caniszczyk Is pullapprove broken? Is there a way to "unstuck" it? |
@stevvooe I kicked it, it should be possible for anyone to click the gear icon in the top right and say "re-sync PR" |
The image spec shouldn't reference real names/addresses in example
content. Switch to the same fake one we use elsewhere. It's like
alternative facts.
Signed-off-by: Jonathan Boulle [email protected]