Need to do version control branch-to-branch deployments? You can kick things off directly from Prodly by creating a pull request (PR). Here's how it works and what to expect.
The PR will include all differences between the source and destination branches.
<aside> <img src="/icons/report_blue.svg" alt="/icons/report_blue.svg" width="40px" />
The pull request automatically includes all differences between the two branches. There is no option to select individual metadata components within the Prodly UI before creation.
</aside>
A PR is automatically created in your repo based on your selected branches.
Optionally select Test Classes which are appended to the PR description based on the selected environment which is used to load the Test Classes from.
<aside> <img src="/icons/report_blue.svg" alt="/icons/report_blue.svg" width="40px" />
Selected test classes are appended to the PR description in the format TestClasses::[Test1, Test2]::TestClasses. Your CI/CD pipeline must be configured to parse this marker and pass the classes to RunSpecifiedTests. This only has effect on branches configured to run RunSpecifiedTests.
</aside>
Once your Pull Request is created:
While in progress and after completion, use the Pull Request History page to drill into the results.
To access the page, click any pull request record from the Pull Request History table to open the Pull Request Details page.
The Pull Request Details page displays pertinent information about the pull request: