codeforboston / codeforboston/maple

Feature Branch CI/CD Workflow - Proposal

Open
#1,298 3 comments 0 reactions 0 assignees View on GitHub
CI/CD tech debt
Dominant language
TypeScript
Stars
56
Forks
175
Avg merge
2d 5h
Merged PRs (30d)
13

Description

For one person, per ticket:

1. Create a local feature branch
1. Do development
1. Push local feature branch -> Create a remote feature branch
1. This creates a feature branch build on Vercel
1. Create a PR
1. Create a well written description of changes, a link to the issue, and things to test (based on the PR template)
1. Ask for review using the feature branch build (isolated to this particular feature)
1. Devs review the code changes, and functionality if no QA
1. Design reviews (if necessary)
1. QA can review if this is a big change
1. Once approved, merge PR directly into a main pipeline - [GitHub Environments](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment) (Require Approvers)
1. Merges into the `dev` environment
1. Then merges into the `prod` environment, after manual approval

Feedback is welcome from anyone, especially @sashamaryl and @mvictor55

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.