Closed ChristianKniep closed 1 year ago
DCO needs to be set on the commit (see the description on DCO error for how to fix it), and I think we want the commit message updated, too.
-s
done with the last commit.
Does MetaHub not have support for any push or query operations (like listing tags), or is that support not OCI compliant?
listing tags should be included, but it's also skipped by others (bundle-bar, azure).
And a quick FYI that the site is hard to read when my desktop is in dark mode:
Yeah, I am getting my hands dirty with JavaScript - I'll get to that eventually...
DCO needs to be set on the commit (see the description on DCO error for how to fix it), and I think we want the commit message updated, too.
-s
done with the last commit.
For https://github.com/opencontainers/oci-conformance/pull/94/commits/ec3e78d8293172538fcba0b9a734a86b07b6c3a4 can you also adjust the commit messages? Should be a git rebase -i ec3e78d8293172538fcba0b9a734a86b07b6c3a4^
, and then change pick
to reword
on the specific commit. You'll need to force push that change.
Does MetaHub not have support for any push or query operations (like listing tags), or is that support not OCI compliant?
listing tags should be included, but it's also skipped by others (bundle-bar, azure).
Bundle bar and Azure each ran the push, discovery, and management tests, which is why it stood out that MetaHub didn't.
I added the DISCOVERY tests while I was at it. Anything else I missed?
Are we allowing squash and merge?
Are we allowing squash and merge?
We'll find out if @jdolitsky yells at me. 😁
✅ Deploy Preview for oci-conformance ready!
Toggle QR Code...
Use your smartphone camera to open QR code link.
To edit notification comments on pull requests, go to your Netlify site settings.