Skip to content

refactor(dev-env)!: replace vipdev.lndo.site with vipdev.site#1984

Open
sjinks wants to merge 2 commits into
trunkfrom
update/site-domain
Open

refactor(dev-env)!: replace vipdev.lndo.site with vipdev.site#1984
sjinks wants to merge 2 commits into
trunkfrom
update/site-domain

Conversation

@sjinks

@sjinks sjinks commented Aug 7, 2024

Copy link
Copy Markdown
Member

Description

This PR replaces vipdev.lndo.site with vipdev.site in the codebase.

The migration from vipdev.lndo.site to vipdev.site will be handled elsewhere (Automattic/vip-container-images#851).

Pull request checklist

New release checklist

Steps to Test

TBD.

@sjinks sjinks added [Status] Needs Review [Status] Needs Docs The feature or update requires an update to our public VIP Documentation DO NOT MERGE labels Aug 7, 2024
@sjinks sjinks self-assigned this Aug 7, 2024
@github-actions

github-actions Bot commented Aug 7, 2024

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Manifest Files

@sjinks sjinks marked this pull request as ready for review August 7, 2024 15:07
@sonarqubecloud

sonarqubecloud Bot commented Aug 7, 2024

Copy link
Copy Markdown

@sjinks

sjinks commented Aug 7, 2024

Copy link
Copy Markdown
Member Author

@sjinks sjinks requested a review from rinatkhaziev August 8, 2024 02:03
@rinatkhaziev

Copy link
Copy Markdown
Contributor

Does this need a test for the migration?

@sjinks

sjinks commented Aug 8, 2024

Copy link
Copy Markdown
Member Author

There is not much to test here... The actual migration happens in the WordPress installation script in Automattic/vip-container-images#851 - specifically, https://github.com/Automattic/vip-container-images/pull/851/files#diff-ad8cc8dcf9efb7506300a53b2cf5754bf370da1daa148bf33304572c6a8050f7R206-R214

@github-actions

github-actions Bot commented Oct 8, 2024

Copy link
Copy Markdown
Contributor

This pull request has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.

This is an automation to keep pull requests manageable and actionable and is not a comment on the quality of this pull request nor on the work done so far. Closed PRs are still valuable to the project and their branches are preserved.

@github-actions github-actions Bot closed this Oct 15, 2024
@sjinks sjinks added [Status] Keep Prevent the "stale" workflow from auto-closing and removed [Status] Stale [Status] Autoclosed [Status] Needs Docs The feature or update requires an update to our public VIP Documentation labels Oct 19, 2024
@sjinks sjinks reopened this Oct 19, 2024
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DO NOT MERGE [Status] Keep Prevent the "stale" workflow from auto-closing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants