GHA-178 Use lock-branch action in automated release workflow (#88)

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

Author: nils-werner-sonarsource

.github/workflows/automated-release.yml

@@ -148,20 +148,12 @@ jobs:
     permissions:
       id-token: write
     steps:
-      - &freeze-branch-secrets
-        id: secrets
-        uses: SonarSource/vault-action-wrapper@v3
+      - name: Freeze branch
+        uses: SonarSource/release-github-actions/lock-branch@2a5ddd698dd3992bf592cf454a04da8fc99fecc5
         with:
-          secrets: |
-            development/github/token/{REPO_OWNER_NAME_DASH}-lock token | lock_token;
-            development/kv/data/slack token | slack_api_token;
-      - &freeze-branch-toggle
-        uses: sonarsource/gh-action-lt-backlog/ToggleLockBranch@v2
-        with:
-          github-token: ${{ fromJSON(steps.secrets.outputs.vault).lock_token }}
-          slack-token: ${{ fromJSON(steps.secrets.outputs.vault).slack_api_token }}
+          branch: ${{ inputs.branch }}
+          freeze: true
           slack-channel: ${{ inputs.slack-channel }}
-          branch-pattern: ${{ inputs.branch }}
       - name: Summary
         if: ${{ inputs.verbose }}
         shell: bash
@@ -398,8 +390,12 @@ jobs:
     permissions:
       id-token: write
     steps:
-      - *freeze-branch-secrets
-      - *freeze-branch-toggle
+      - name: Unfreeze branch
+        uses: SonarSource/release-github-actions/lock-branch@2a5ddd698dd3992bf592cf454a04da8fc99fecc5
+        with:
+          branch: ${{ inputs.branch }}
+          freeze: false
+          slack-channel: ${{ inputs.slack-channel }}
       - name: Summary
         if: ${{ inputs.verbose }}
         shell: bash

CLAUDE.md

@@ -13,8 +13,8 @@ Related Jira tickets for this project are tracked in the **GHA** (GitHub Automat
 ## Branching
 
 **Critical:** Changes must always be made on a feature branch, never directly on `master`. Before any commit, verify you are not on `master`.
-- If on `master`, create a new branch using the format: `ab/<feature-name>` (e.g., `ab/add-slack-notifications`)
-- The prefix `ab` represents the developer's initials (first letter of first name + first letter of last name)
+- If on `master`, create a new branch using the format: `<username-prefix>/<feature-name>` (e.g., `ab/add-slack-notifications`)
+- Ask for the prefix to use from the team if unsure (e.g., `ab/` for Antoine B., `js/` for Jean S., etc.)
 - Adapt `<feature-name>` based on the task/prompt (use lowercase, hyphen-separated)
 - If already on a feature branch, do not create a new branch—continue working on the current branch