Skip to content

Commit 6775bfe

Browse files
committed
chore: tweak message
1 parent 539f60e commit 6775bfe

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

content/docs/tutorials/github-release-cicd-workflow.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ description: 'Learn how to automate database release CI/CD using GitHub Actions
1212
This tutorial shows you how to build an automated database release pipeline using GitHub Actions and Bytebase API. You'll learn to:
1313

1414
1. Create a streamlined database release workflow where you can:
15+
1516
- Submit SQL migrations through GitHub
1617
- Automatically run SQL reviews on pull requests
1718
- Auto-create and deploy Bytebase releases when merging to `main`
@@ -31,7 +32,7 @@ This tutorial code repository is at [https://github.com/bytebase/release-cicd-wo
3132
- [Docker](https://www.docker.com/) installed
3233
- An [ngrok](https://ngrok.com/) account
3334

34-
## Streamline database release workflow
35+
## Automatic Rollout across environments
3536

3637
### Step 1 - Start Bytebase with ngrok
3738

@@ -212,9 +213,10 @@ To create migration files to trigger release creation, the files have to match t
212213

213214
The rollout pipeline stages are created on demand in the **Rollout** step.
214215

215-
## Manual Rollout by Stage (Pro or Enterprise Plan)
216+
## Manual Rollout by Environment (Pro or Enterprise Plan)
216217

217-
If you have **Pro** or **Enterprise** plan, you can manually rollout the release to the database by stage.
218+
In the previous section, once the PR is merged, we create a release and roll out it to both test and prod environments automatically.
219+
You can also manually control the rollout by stage if you have **Pro** or **Enterprise** plan.
218220

219221
1. Upgrade your Bytebase plan to **Pro** or **Enterprise** plan, assign the license to your instances.
220222

0 commit comments

Comments
 (0)