Fix info.json keys in approved CC guide #6382
Open
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
Flame442
added
the
Type: Bug
github-actions
bot
added
Category: Docs - For Developers
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.
Description of the changes
Like many people, I simply referenced other people's cogs to make my
info.jsons, and an extra phantom key from the V2 days made its way into our docs. I removed thenamekey from both the repo and cog requirements, and added the conditionalmin_python_versionkey since lots of cogs lately have needed that one.Technically the cookie cutter repo and the policies should also be updated, but I don't want to do that :(
Have the changes in this PR been tested?
Yes