Project description and short intro goes here.
| Environment | Branch | URL | Hostname |
|---|---|---|---|
| Production | main | https://example.com | prod.example.com |
| Staging | staging | https://staging.example.com | staging.example.com |
| Development | develop | https://dev.example.com | dev.example.com |
| Name | Github Username |
|---|---|
| Name | @github_username |
| Name | Github Username |
|---|---|
| Name | @github_username |
main
- For bug -
fix/issue-nameFor example,fix/phpcs-errors - For feature -
feature/issue-nameFor example,feature/add-plugin
- Title should be same as Issue title. Also add issue number before title. For example,
GH-3 Setup initial theme. - Add proper description.
- Assign reviewer.
- Create draft pull request for work in-progress PR and don't add
WIP:in PR title. - PR should have one approval.
List down tests created for the project and details on how to execute them locally.
- PHP Unit tests if any.
- Behat tests if any.
- GitHub actions/travis/circleci etc. CI test cases if any.
Notes about linting to be followed in project.
Add details about JIRA / ActiveCollab / GitHub project in use.
Example: Plugin settings that need to be updated in dev/staging sites.
| Title | Name | Disable on dev site? | Notes |
|---|---|---|---|
| Jetpack by WordPress.com | jetpack | No | Enable Jetpack Dev Mode |
| AWS SES wp_mail drop-in | aws-ses-wp-mail | No | Check that AWS_SES_MAIL_* constants are not present in wp-config |
Add details of apps and integrations installed for the repo.
If you are setting up the repo, read: REPO-SETUP-GUIDE.md
Please read the skeleton repo guide to understand the structure of repo: SKELETON-GUIDE.md