This repository has been archived by the owner on Dec 27, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Theme Deployment Workflow
Nathan Arthur edited this page Jun 13, 2019
·
24 revisions
Theme | Links | development | production | |
---|---|---|---|---|
All themes | ||||
ALPS | ||||
Banyan | ||||
Carmel | ||||
Gumwood | ||||
Iris | ||||
Ivy | ||||
LUH | ||||
Nightingale | ||||
Oak | ||||
Obsidian | ||||
Organic | ||||
Prairie | ||||
Prototype | ||||
Rubix | ||||
Spruce | ||||
Willow |
- Review all issues
- Review all pull requests
- Review all branches
- Update thumbnails in development
- Compare production...development and create a pull request if there are differences
- Request review on the PR
This stage should be done by someone different from the person who did the previous stages.
- Pull and activate latest version of development
- Visually review all components in styleguide (usually at
/admin/theme/view/layout/styleguide.html
) - Visually review all theme layouts
- Ask for any needed changes in the PR
- When satisfied, approve PR
For more information on testing, see manual_testing.md
- Once the PR has been approved, merge development into production
Sites used for reviewing need to be using the development branch for themes. When using one of the below sites, reinstalling the theme should update the theme with the latest commits on the remote development branch.
- acc.simpleupdates.com
- crystalh.sites.simpleupdates.com
- next.simpleupdates.com
- http://www.walktopeace.com/ (version 2)
- Add new theme to all-PRs link
- Add new theme to all-issues link
- Duplicate a theme row
- Decide on three-letter abbreviation
- Update all new-row links with the new abbreviation
- Add entries to link lists for all the identifiers in the new row
- Test all new-row links