Repository: update to use WordPress own repository #7
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
Since this object lists info about the WordPress software, it may make more sense to use the WordPress repository there.
|
I think you are right... but maybe I should add a meta then, to give a hint to this plugin, because WordPress does not (yet) support NodeInfo out of the box... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I was looking at your plugin, and was surprised to see the repository for the plugin listed for the repository key. Since this object lists info about the WordPress software, wouldn't it make more sense to use the WordPress repository there?
I may be missing something obvious though, so correct me if I'm wrong :)