Remove mapped_specialist_topic_content_id

[unoduetre]

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

This application is owned by the publishing platform team. Please let us know in #govuk-publishing-platform when you raise any PRs.

Follow these steps if you are doing a Rails upgrade.

Warning

The following PR in the whitehall repository must be merged first.

What

As part of work to retire specialist topics, we temporarily stored a mapping between the archived specialist topic and its document collection conversion. We should remove this once we’re done.

Why

To keep the system clean and avoid unnecessary data.

Trello card

[beccapearce]

This one looks good too. Again it would be great to make the commit messages distinct. (I know one is just generated), I usually just use Run rake build_schemas for the second commit so people know they can not pay it too much attention.

[unoduetre]

This one looks good too. Again it would be great to make the commit messages distinct. (I know one is just generated), I usually just use Run rake build_schemas for the second commit so people know they can not pay it too much attention.

They are distinct, because of the second line, which is not visible by default here (you'd need to click on ...), but it is visible in the commit list.

[beccapearce]

yep yep, I see the rest of the commit message. it would be nice to have it in the title of the commit I think. Just thinking about scrolling down the commits in the github GUI where the extended commit isn't visible by default.

[unoduetre]

@beccapearce I've updated commit messages and PR name.

[hannako]

Thanks @unoduetre it's great to see this almost gone!

You can reference that the work reverts #2385

And whilst it seems like a nitpick, I do agree with Becca's comment about simple scannable commit titles. You can see the titles for the original implementation as a guide.

[beccapearce]

Looks great to me! 💪

[JonathanHallam]

Looks good to me, thank you :)