chore(wordpress): drop the svn/tags copy from git - #60
Merged
Merged
Conversation
…ress@<version> GitHub releases
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
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.
Background
Releasing the plugin is now merge-only (#57), except one manual step: committing
wordpress/svn/tags/<version>/to git after each release, as a copy of WordPress.org. Every release is already recorded as awordpress@<version>GitHub release on the commit it was published from, so the copy duplicates that history.Changes
wordpress/svn/tags/leaves git and is ignored (the manual SVN fallback still creates it locally)wordpress/README.mdend at "Merge", and say where published versions are recordedNotes
wordpress/svn/, so the WordPress release workflow runs: 1.2.1 is already published and the readme and assets match, so it publishes and announces nothing (the publish preview on this PR shows the same)