Table of Contents
Merge Multidev to Dev
Preparing for a request
In order for you to get your changes up so we can test them, you need to deploy a Multidev and apply your changes there first. Once your changes are on the Multidev, test them against the latest available upstream updates. Then a Merge Multidev to Dev request needs to be submitted in your college Slack channel. You can expect your changes to be on the development environment by the end of the next business day. After your changes pass our code review process we will apply your changes to the staging/test environment for further review. Expect your changes to move from stage to the production environment usually with the next morning code push if everything goes well with the further review on stage.
Creating a Multidev
More information about Multidev environments is available in the Pantheon documentation.
Login to your Pantheon Dashboard
Click the Multidev tab
Click the Create an Environment button
On the Create Multidev Environment modal that pops up, Name the New Environment and Git Branch and under the Cone Database and Files From: drop-down select a database.
Click the Create Environment button
Wait
Once it is done you will see:
Click the name of your Multidev to open its dashboard
Launching your Multidev Site
Starting Notes
On your Multidev dashboard, click the Visit {{ name of your Multidev }} Site button
Cloning a Multidev using Git
Starting Notes: Git
Click the Clone with Git button
Click the Show Detailed Instructions link
Follow the Example to make your changes and push them back into the Multidev
Visit the Local Development Stack article to read more about testing your changes locally.
Related Articles
Select the table below to edit…
Add Comment