feat: update copy from Twitter to X and refresh icons (DPS-4429) #1552
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
wojciechdudek-livechat
approved these changes
Feb 13, 2025
|
looks good |
|
🎉 This PR is included in version 2.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Deploy preview
Scroll down to the checks section for the link to the deploy preview of your branch.
Links
Link your Jira ticket.
Description
The task involves updating all references to "Twitter" in the application to "X" and replacing any outdated Twitter icons with the current X branding. Specifically:
Update Copy: Replace all instances of "Twitter" with "X".
Update Icons: Replace old Twitter logos/icons with the new X branding.
Check Social Links: Ensure all Twitter profile or sharing links still function correctly.
Versioning
Pull request titles should comply with the Conventional Commits specification. This is required to update the project's version.
Review and release
Apply changes and resolve conflicts. Once the described functionality lands on prod, let us know on #platform-docs-releases that your PR is ready for release. We will merge and publish the changes.