Update/community files #1
Merged
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
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 Change
This PR adds the standard set of GitHub community files, updates WordPress.org requirements to the main plugin file and readme.txt, as well as updated composer.json and package.json standard items.
One item I didn't handle in this PR, but can update the branch to include, is renaming
plugin.phptogutenbridge.phpas well as any references fromplugin.phptogutenbridge.php. If that renaming is desired, then I can work to make those changes in this PR as well. Just let me know... thanks!Alternate Designs
n/a
Benefits
Ensures the plugin follows our Open Source Best Practices.
Possible Drawbacks
none identified
Verification Process
Manually verified via the GitHub Desktop UI.
Checklist:
Applicable Issues
n/a
Changelog Entry