Add a rake task to reslug an edition [WHIT-3475] #11485
Open
eYinka wants to merge 1 commit into
Open
Conversation
We had a case where a superseded edition had the same slug as a new document. This meant that the new document could not be published under the ideal slug until the superseded edition frees the slug. The new document's slug had had '--2' appended to it, which is not ideal. I've now added a rake task to reslug an edition, which will allow us to fix issues like this. Instead of receiving the old slug as an argument, the task receives the edition's ID, just to be sure we're reslugging the intended edition. Usage: `bundle exec rake reslug:edition[12345,new-slug]`
eYinka
force-pushed
the
add-rake-task-to-reslug-an-edition
branch
from
c27df13 to
83144e9
Compare
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
1 participant
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.
We had a case where a superseded edition had the same slug as a new document. This meant that the new document could not be published under the ideal slug until the superseded edition frees the slug. The new document's slug had had '--2' appended to it, which is not ideal.
I've now added a rake task to reslug an edition, which will allow us to fix issues like this. Instead of receiving the old slug as an argument, the task receives the edition's ID, just to be sure we're reslugging the intended edition.
Usage:
bundle exec rake reslug:edition[12345,new-slug]JIRA
This application is owned by the Whitehall Experience team. Please let us know in #govuk-whitehall-experience-tech when you raise any PRs.
Follow these steps if you are doing a Rails upgrade.