docs: update link

Author: tianzhou

content/blog/bytebase-vs-cloudbeaver.md

@@ -158,7 +158,7 @@ On the other hand, the more common way to change the schema is to use **Schema E
 
 - **CloudBeaver**: In theory, you can build GitOps solution via the GraphQL API, but there is no mature solutions.
 
-- **Bytebase**: [GitOps best practice](https://github.com/bytebase/api-example/tree/main/data-security) to configure every aspect of database security.
+- **Bytebase**: [GitOps best practice](https://github.com/bytebase/database-security-github-actions-example) to configure every aspect of database security.
 
 ## Summary
 

content/blog/top-open-source-sql-clients.md

@@ -88,7 +88,7 @@ Aforementioned tools are all client-side SQL editors for individual use. What if
 - **Data masking**. You may want to prevent users seeing sensitive data.
 - **Request and review workflow**. You want users go through a ticketing process to request the access rights.
 - **Audit logging**. You want to capture all operations performed on the database.
-- **Policy as Code (GitOps)**. Permission control and masking policies can be [codified](https://github.com/bytebase/api-example/tree/main/data-security) and integrated with your existing DevOps pipeline.
+- **Policy as Code (GitOps)**. Permission control and masking policies can be [codified](https://github.com/bytebase/database-security-github-actions-example) and integrated with your existing DevOps pipeline.
 
 All above requirements call for a server-side solution. And that's what [Bytebase SQL Editor](/sql-editor) provides.
 

content/blog/what-is-database-devsecops.md

@@ -75,7 +75,7 @@ efficient querying for authorized users.
 
 <HintBlock type="info">
 
-Unlike client-side solutions, Bytebase is a server-side solution providing [access control](/docs/security/database-permission/overview/), [dynamic data masking](/docs/security/data-masking/overview/), [audit logging](/docs/security/audit-log/). You can also [codify these data security policies (Policy-as-Code)](https://github.com/bytebase/api-example/tree/main/data-security).
+Unlike client-side solutions, Bytebase is a server-side solution providing [access control](/docs/security/database-permission/overview/), [dynamic data masking](/docs/security/data-masking/overview/), [audit logging](/docs/security/audit-log/). You can also [codify these data security policies (Policy-as-Code)](https://github.com/bytebase/database-security-github-actions-example).
 
 </HintBlock>
 

content/docs/api/issue.md

@@ -21,7 +21,7 @@ title: Issue
 
 ## How to create an issue
 
-Code sample: https://github.com/bytebase/github-action-example/blob/main/.github/actions/upsert-issue/index.ts#L68-L75
+Code sample: https://github.com/bytebase/cicd-github-actions-example/blob/main/.github/actions/upsert-issue/index.ts#L68-L75
 
 ```go
 // Create plan

content/docs/security/data-masking/overview.md

@@ -12,7 +12,7 @@ organizations to protect sensitive data from being exposed to unauthorized users
 
 <HintBlock type="info">
 
-You can configure the masking policies from UI or via API. Check out [this GitOps example](https://github.com/bytebase/api-example/tree/main/data-security) to see how to codify the masking policies.
+You can configure the masking policies from UI or via API. Check out [this GitOps example](https://github.com/bytebase/database-security-github-actions-example) to see how to codify the masking policies.
 
 </HintBlock>
 

content/docs/tutorials/data-masking.md

@@ -21,7 +21,7 @@ from being exposed to unauthorized users.
 <HintBlock type="info">
 
 This tutorial covers configuration via UI console. You can also codify the masking policies, check
-out [this sample](https://github.com/bytebase/api-example/tree/main/data-security).
+out [this sample](https://github.com/bytebase/database-security-github-actions-example).
 
 </HintBlock>
 

content/docs/tutorials/github-ci.md

@@ -9,7 +9,7 @@ estimated_time: '30 mins'
 description: 'In this article, you will delve into a practical example from Bytebase, demonstrating how to automate database schema change workflow using GitHub Actions and Bytebase API.'
 ---
 
-> Tutorial repository [https://github.com/bytebase/github-action-example](https://github.com/bytebase/github-action-example)
+> Tutorial repository [https://github.com/bytebase/cicd-github-actions-example](https://github.com/bytebase/cicd-github-actions-example)
 
 Developers like to keep their schema migration scripts in Git along with the application code. Thus
 the migration scripts will be reviewed and version-controlled in the same way as the application code.
@@ -125,7 +125,7 @@ and emit GitHub inline annotations for each advice and mark the check as failed
       ...
 ```
 
-We create a [PR](https://github.com/bytebase/github-action-example/pull/15) with several SQL files, and it triggers both `bytebase-sql-review.yml` and `bytebase-check-migration-status.yml`. After these checks are completed, the PR is blocked due to failures.
+We create a [PR](https://github.com/bytebase/cicd-github-actions-example/pull/15) with several SQL files, and it triggers both `bytebase-sql-review.yml` and `bytebase-check-migration-status.yml`. After these checks are completed, the PR is blocked due to failures.
 
 ![gh-pr1-blocked](/content/docs/tutorials/github-ci/gh-pr1-blocked.webp)
 

content/docs/tutorials/sql-review.md

@@ -142,7 +142,7 @@ You may call [Bytebase API](/docs/api/sql-review/) in your internal portal or Gi
   Sample portal to call Bytebase API to trigger schema change including SQL Review.
   ![bb-api](/content/docs/tutorials/sql-review/bb-api.webp)
 
-- [🐙 API in GitHub Actions Example](https://github.com/bytebase/github-action-example)
+- [🐙 API in GitHub Actions Example](https://github.com/bytebase/cicd-github-actions-example)
 
   Sample github custom actions to call Bytebase API to coordinate the schema migration in Bytebase with the GitHub PR workflow.
   ![bb-gh-action](/content/docs/tutorials/sql-review/bb-gh-action.webp)