gh-actions-doc-auto-merge-develop

You can automatically merge a production branch into a documentation branch by creating a GitHub Actions workflow that triggers on production updates and performs the merge. This Skill generates that workflow file to sync changes automatically.

Duplicate GitHub Actions workflow files occur when sync workflows are repeatedly created without checking existing configurations. This Skill prevents duplicates by checking the .github/workflows/ directory for an existing sync workflow before generating a new one.

The best way to keep a docs deploy branch updated with main is to automate the branch sync using GitHub Actions. This Skill automates the merge process, ensuring your documentation branch reflects production after each update.

You configure CI CD for automatic branch sync by generating a workflow file named sync-<production>-to-<doc>.yml in your repository. This workflow handles the automated merge from your production branch into your doc branch.

No, you do not need to manually trigger the workflow to merge production into doc. The generated GitHub Actions workflow automatically initiates the merge whenever changes are pushed to the production branch.