-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release version 0.10.0 #102
Merged
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
By default, jquery UI has a 300ms timeout, by increasing it to 600ms it reduces the potential to flood the server with requests.
1. Remove stray spaces 2. Deduplicate blank lines 3. Obey EditorConfig including tabs vs. spaces and line end characters 4. Don't export development files 5. Add LICENSE file Co-authored-by: Gary Jones <github@garyjones.io>
Without this, each CI job actually uses the latest version of WP, regardless of the version named in the job title.
With the later versions of Ubuntu that the CI jobs run on, comes newer versions of MySQL, which means this change is needed. Once PHP 7.3 support is removed, this workaround can also be removed.
…pported-versions
- Move screenshots to subdirectory for later easier deployment to WordPress.org plugin repository. - Consolidate information from `readme.txt` into `README.md`, and remove `readme.txt` file. - Move changelog content into a new `CHANGELOG.md` file.
Adds scripts to make it easier to bump the version numbers in various places. e.g. `npm run bump:minor`.
These development files are then not included when doing a release archive from GitHub, or a Composer pull down with `--prefer-dist`. Keep it to production-critical files (and a readme) only.
When pushing to WordPress.org SVN plugin repository, no development files are needed there (they aren't needed in production when someone grabs the plugin from WordPress.org) - these should be kept on the GitHub repo for developers.
This action, with the saved repository secrets, allows the pushing of a new GitHub release to WordPress.org automatically.
GitHub already handled the redirect, so there's no change in behaviour here.
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.
I'll wait until Monday to merge, tag, and release.