-
Notifications
You must be signed in to change notification settings - Fork 664
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
Removing Link Introduction #856
Conversation
spec.md
Outdated
@@ -42,7 +41,7 @@ Typically, these manifests may provide different implementations of the image, p | |||
|
|||
![](img/build-diagram.png) | |||
|
|||
Once built the OCI Image can then be discovered by name, downloaded, verified by hash, trusted through a signature, and unpacked into an [OCI Runtime Bundle](https://github.com/opencontainers/runtime-spec/blob/master/bundle.md). | |||
Once built the OCI image can then be discovered by name, downloaded, verified by hash, trusted through a signature, and unpacked into an [OCI Runtime Bundle](https://github.com/opencontainers/runtime-spec/blob/master/bundle.md). |
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.
I see OCI Image
used throughout the spec, so I don't know if I agree with this line.
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.
There are also a lot of lowercase - I guess I don't see it as a proper noun so I made it lowercase. But if you are requesting to make it capital again, happy to do that.
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.
All set.
There doesn't seem to be an introduction in this file (and the link goes to itself?) so I think we probably want to remove it (or link to an introduction elsewhere?) Signed-off-by: vsoch <[email protected]>
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.
LGTM
It looks like the DCO/signoff may have an issue with a difference in the commit email and the signoff email? not sure |
I did change both emails to be my GitHub no reply email when I left Stanford. |
Where do you see the issue? It looks green to me! |
https://pullapprove.com/opencontainers/image-spec/pull-request/856/requirements/ |
@vbatts GitHub holds an internal representation of that address with and without the number. It's kind of complicated but without signing with the number it doesn't link to me, so the gpg key actually has all of those emails (and my original stanford) so I'm not sure why one is explicitly chosen. I wrote more about it here: https://vsoch.github.io/2021/signing-with-myself/. |
I did create the original commit in the GitHub interface and then pulled and rebased, so that might be why the two are different? I can close here and re-do again if you want... this seems like an extraordinary amount of work to just remove one line! I'm not sure why it's always so hard to contribute to these repos :/ |
Fair. And we have 2 DCO checks, and only one fail? 🤔 |
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.
🌃
@caniszczyk do we need the pullapprove DCO check also, since it's being a little strict? |
There doesn't seem to be an introduction in this file (and the link goes to itself?) so I think we probably want to remove it (or link to an introduction elsewhere?)