Primo Studio Reviewer Guide
The Primo Studio GitHub Repository is monitored by volunteers who are members of the Ex Libris User Group of North America and the International Group of Ex Libris Users.
The volunteers monitor the repository for add-ons sumbitted by Developers to the submit_here branch
When a pull request is submitted, it will be assigned to a reviwer. Below are the steps reviewers follow:
-
Sign into GitHub and go to primousers/primostudio
-
Contributors submits pull request to the submit_here branch. Navigate to the Submit_here branch to view the pull request to view the request.
*Sometimes Developers submit their pull request to the master branch, if this is the case, we will need to ask them to resubmit to the submit_here branch.
-
Go to Primo Studio
-
Open up Primo Studio and use the version you prefer, either your own, or the central package. If using your own, add your Primo UI base url and view ID
-
Add &branch=submit_here to the URL
-
Click on "Add ons" and try to install the add on.
*If it requires an API key, you can ask the contributor to provide one. *If it requires a Primo Public Key, you can sign into the Developer’s network and get this from you list of API keys (you may have to create this if it doesn’t already exist)
-
If the add on works as expected, it can be pushed form the "submit_here" branch to the "dev" branch (see the instructions below). If there are any issues or concerns with the add on, ask another volunteer to test it. If it does not seem to install or work as expected, contact the developer who submitted the pull request through GitHub.
-
Once an add on has been tested, the Primo Studio GitHub pull request in the “submit_here” branch.
.
-
Add a review with your comments and push to the dev branch. *At least one review is necessary before pushing to the dev branch.
-
One other volunteer should confirm that it works, and check anything else that the first reviewer wasn’t sure about.
-
Push to the master branch.