.pullapprove.yml: Add distribution-spec-maintainers #53
Conversation
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
Catching up with [1]. Also mention the new project in GOVERNANCE.md. I'd still rather drop the parenthetical entirely and link to a place that listed OCI Projects, but we don't have a canonical target for that yet (opencontainers/tob#2) and the current closest instance seems to be the GitHub section in [2] (which doesn't have the "OCI Project" words). [1]: opencontainers/tob#35 [2]: https://www.opencontainers.org/community Signed-off-by: W. Trevor King <[email protected]>
wking
force-pushed
the
distribution-maintainers
branch
from
cbfea6d to
d3b62b7
Compare
|
I've just squashed in an update to the |
|
The PullApprove failure is:
We've had similar issues before. Perhaps @caniszczyk remembers the appropriate way to kick PullApprove? |
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.
Catching up with opencontainers/tob#35.
We'll want this if we're trying to continue with the “two maintainers from every OCI Project have LGTMed” approach initially adopted in f412693 (#29). See #41 for some other maintenance ideas; but as long as that's open I think we need to continue with the current pattern.