chore: make config name more verbose (#48)

Author: RainbowDashy

.github/workflows/chatops-migrate.yml

@@ -22,9 +22,9 @@ jobs:
       targets: ${{ steps.parse.outputs.targets }}
     steps:
       - name: Write command config
-        # write a config.yaml file to runner temp directory
+        # write a bytebase-action-config.yaml file to runner temp directory
         run: |
-          cat <<EOF > ${{ runner.temp }}/config.yaml
+          cat <<EOF > ${{ runner.temp }}/bytebase-action-config.yaml
           test:
             stage: environments/test
             targets:
@@ -40,7 +40,7 @@ jobs:
           COMMENT="${{ github.event.comment.body }}"
           echo "Comment: $COMMENT"
           
-          CONFIG_FILE="${{ runner.temp }}/config.yaml"
+          CONFIG_FILE="${{ runner.temp }}/bytebase-action-config.yaml"
           
           # Get list of valid environments from config
           VALID_ENVS=$(yq eval 'keys | join(", ")' "$CONFIG_FILE")

README.md

@@ -72,7 +72,7 @@ This workflow enables ChatOps-style deployments through PR comments. Team member
 
 #### Configuration
 
-1. **Define environments in the workflow**: Edit the `config.yaml` generation step to define your environments and their database targets.
+1. **Define environments in the workflow**: Edit the `bytebase-action-config.yaml` generation step to define your environments and their database targets.
 
 > [!NOTE]
 > The top-level keys (e.g., `test`, `prod`) are used as GitHub Actions job environments, so they must match the environment names configured in your repository settings.
@@ -81,7 +81,7 @@ This workflow enables ChatOps-style deployments through PR comments. Team member
 ```yml
       - name: Write command config
         run: |
-          cat <<EOF > ${{ runner.temp }}/config.yaml
+          cat <<EOF > ${{ runner.temp }}/bytebase-action-config.yaml
           test:
             stage: environments/test
             targets: