chore: changed repo name (#558)

Author: d-bytebase

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/database-security-github-actions-example) to configure every aspect of database security.
+- **Bytebase**: [GitOps best practice](https://github.com/bytebase/example-database-security) to configure every aspect of database security.
 
 ## Summary
 

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

@@ -86,7 +86,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/database-security-github-actions-example) and integrated with your existing DevOps pipeline.
+- **Policy as Code (GitOps)**. Permission control and masking policies can be [codified](https://github.com/bytebase/example-database-security) 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/database-security-github-actions-example).
+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/example-database-security).
 
 </HintBlock>
 

content/changelog/bytebase-3-3-0.md

@@ -14,7 +14,7 @@ To request our SOC 2 Type 1 report, please email [[email protected]](mailto:s
 
 ## 🔔 Breaking Changes
 
-- Simplify data masking, both UI and API are affected, check [docs](/docs/security/data-masking/overview/) and [API examples](https://github.com/bytebase/database-security-github-actions-example/tree/main/masking) for details. Behavior changes:
+- Simplify data masking, both UI and API are affected, check [docs](/docs/security/data-masking/overview/) and [API examples](https://github.com/bytebase/example-database-security/tree/main/masking) for details. Behavior changes:
   - Global masking takes precedence over column masking. Previously, column masking takes precedence over global masking.
   - Eliminate masking levels. For both global masking and column masking, you now configure the associated semantic type. Semantic type in turn maps to the corresponding masking algorithm.
 

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/database-security-github-actions-example) 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/example-database-security) to see how to codify the masking policies.
 
 </HintBlock>
 

content/docs/tutorials/data-masking.md

@@ -20,7 +20,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/database-security-github-actions-example/tree/main/masking).
+out [this sample](https://github.com/bytebase/example-database-security/tree/main/masking).
 
 </HintBlock>
 

content/docs/tutorials/github-action-data-masking-part1.md

@@ -31,11 +31,11 @@ In this tutorial, you'll learn how to automate database masking policies using G
 - Manage data masking rules as code
 - Automatically apply masking policies when PRs are merged
 
-Here is [a merged pull request](https://github.com/bytebase/database-security-github-actions-example/pull/81) as an example, for this tutorial, only "Semantic Type and Global Masking Rule" is covered.
+Here is [a merged pull request](https://github.com/bytebase/example-database-security/pull/81) as an example, for this tutorial, only "Semantic Type and Global Masking Rule" is covered.
 
 <HintBlock type="info">
 
-The complete code for this tutorial is available at: [database-security-github-actions-example](https://github.com/bytebase/database-security-github-actions-example)
+The complete code for this tutorial is available at: [example-database-security](https://github.com/bytebase/example-database-security)
 
 </HintBlock>
 
@@ -68,7 +68,7 @@ Before you begin, make sure you have:
 
 ### Step 4 - Configure GitHub Actions
 
-1. Fork [Database Security GitHub Actions Example](https://github.com/bytebase/database-security-github-actions-example).
+1. Fork [Database Security GitHub Actions Example](https://github.com/bytebase/example-database-security).
 
 1. Click **Settings** and then click **Secrets and variables > Actions**. Add the following secrets:
 
@@ -78,7 +78,7 @@ Before you begin, make sure you have:
 
 ### Step 5 - Understanding the GitHub Workflow
 
-Let's dig into the GitHub Actions workflow [code](https://github.com/bytebase/database-security-github-actions-example/blob/main/.github/workflows/1-bb-masking-semantic-type-global.yml):
+Let's dig into the GitHub Actions workflow [code](https://github.com/bytebase/example-database-security/blob/main/.github/workflows/1-bb-masking-semantic-type-global.yml):
 
 1. **Trigger**: Workflow runs when PRs are merged to `main`.
 

content/docs/tutorials/github-action-data-masking-part2.md

@@ -29,11 +29,11 @@ In this tutorial, you'll learn how to automate column masking and masking exempt
 - Manage data masking rules as code
 - Automatically apply masking policies when PRs are merged
 
-Here is [a merged pull request](https://github.com/bytebase/database-security-github-actions-example/pull/81) as an example.
+Here is [a merged pull request](https://github.com/bytebase/example-database-security/pull/81) as an example.
 
 <HintBlock type="info">
 
-The complete code for this tutorial is available at: [database-security-github-actions-example](https://github.com/bytebase/database-security-github-actions-example)
+The complete code for this tutorial is available at: [example-database-security](https://github.com/bytebase/example-database-security)
 
 </HintBlock>
 

content/docs/tutorials/github-action-data-masking-part3.md

@@ -31,7 +31,7 @@ In this tutorial, you'll learn how to automate data classification using GitHub
 
 <HintBlock type="info">
 
-The complete code for this tutorial is available at: [database-security-github-actions-example](https://github.com/bytebase/database-security-github-actions-example)
+The complete code for this tutorial is available at: [example-database-security](https://github.com/bytebase/example-database-security)
 
 </HintBlock>