As a developer, I want to update GitHub Actions workflow after branch rename so that deployments target the correct release branch

[kiyotis]

Situation

After branch rename (main→release, develop→main), the GitHub Actions workflow still references old branch names:

• Workflow triggers on refactor-extract-workflow-scripts (temporary test branch)
• Deployment target is test-to (temporary test branch)
• These need to be updated to use the new branch structure where main is the development branch and release is the production release branch

Pain

Developers cannot deploy changes to the actual release branch after the rename. The workflow continues deploying to test-to, which is only meant for temporary testing. Without this update, the new branch strategy (main for development, release for controlled releases) cannot function as intended.

Benefit

• Developers can merge changes to main and have them deploy to test-to for validation
• Maintainers can control release timing by merging main → release when ready
• The workflow aligns with the new branch strategy where release timing is human-controlled
• Team follows GitHub Flow best practices while maintaining release control

Success Criteria

• .github/workflows/sync-to-nabledge.yml trigger changed from refactor-extract-workflow-scripts to main
• Deployment target changed from test-to to release
• Test deployment to release branch succeeds via workflow
• Documentation updated to reflect new branch strategy (main → release)
• Workflow validated by pushing test change to main and verifying deployment to release branch

Context

This work follows completion of:

• Step 1: PR Refactor GitHub Actions workflow and improve documentation #23 merged to develop (workflow refactoring)
• Step 2: Branch rename completed (main→release, develop→main, default branch set to main)