Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

README.md: update development workflow #114

Merged
merged 1 commit into from
Jan 29, 2024
Merged

README.md: update development workflow #114

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,11 @@ additional layer of control and verification in the beta/prod environment.
1. Whenever creating new branch for your changes, first, remember to checkout to
up to date `develop` branch.
2. After pushing changes to your branch, set a Pull Request to `develop` branch,
instead of `main`. Reporter will verify patch and publish beta env to the
production later.
instead of `main`. Reporter will verify patch and publish beta env.
* beta website: <https://beta.3mdeb.com/>
3. After successful deployment on the beta environment, if a whole set of
patches is merged in the `develop` branch, open a new PR to `main`. The
reporter will verify changes and publish prod env.
* prod website: <https://3mdeb.com/>

> **NOTE**: If you forgot about rule Ad. 1, you can change the source branch
Expand Down
Loading