forked from Automattic/vip-go-skeleton
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Rebased 'master' onto 'production' #13
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
.gitignore: Remove remnants of debug-bar
…ence on docs.wpvip.com site
The Twenty Twenty Two theme was reverted from v1.2 to v1.0 in Automattic#93. This brings it up to the latest as of March 2023, which is v1.4.
Updates the Twenty Twenty Three theme, added in Automattic#91, from v1.0 to v1.1.
Bump down WP_POST_REVISIONS to 100, add a link to the technical reference on docs.wpvip.com site
…hree-11 Update Twenty Twenty Three to v1.1
…wo-14 Update Twenty Twenty Two to v1.4
See https://github.com/Automattic/VIP-Coding-Standards/releases/tag/3.0.0 No need for the PHPCS Composer plugin to be named, as this is already included via the PHPCSUtils package that VIPCS requires.
Updates [Twenty Twenty Two](https://wordpress.org/themes/twentytwentytwo/) theme, last updated in Automattic#97, to v1.4, released 13 June 2023.
Updates the [Twenty Twenty Three](https://wordpress.org/themes/twentytwentythree/) theme, last updated in Automattic#98, from v1.1 to v1.2, released 8 Aug 2023.
Release codespaces publicly
Updates links to VIP documentation. (All of them were returning HTTP 301 instead of 200. one was pointing to a now-unrelated page; all the rest were redirecting correctly, so for those cases, this update just removes a hop.)
Updates Twenty Twenty Two theme, last updated in Automattic#103, to v1.8, released 16 July 2024.
Updates Twenty Twenty Four theme, last updated in Automattic#104, from v1.0 to v1.2, released 16 July 2024.
Updates Twenty Twenty Three theme, last updated in Automattic#102, from v1.2 to v1.5, released 16 July 2024.
making it more clear that VIP offers an unlimited post revision history
…d site" This reverts commit 5e1841c.
Signed-off-by: Riddhesh Sanghvi <[email protected]>
Signed-off-by: Riddhesh Sanghvi <[email protected]>
This reverts commit 98eb9f8.
This reverts commit 0a29b83.
mrrobot47
approved these changes
Nov 21, 2024
- Removed extra core themes.
@mrrobot47 I've updated the PR and also removed extra older themes. Could you take a look once again. |
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.
IMPORTANT: Please do not create a Pull Request without creating an issue first.
Types of changes
What types of changes do your code introduce to the project?
Put an
x
in the boxes that applyDetails
Checklist
Put an
x
in the boxes that apply.Further comments (if needed)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Closing issues
Fixes: #ISSUE_NUMBER (For bug reports)
or
Closes: #ISSUE_NUMBER (For feature requests)