Skip to content

feat: Add automatic backporting to staging for deployment workflows#132

Merged
crispy101 merged 2 commits intomainfrom
feature/DO-2013_auto_backporting_to_staging
Apr 15, 2026
Merged

feat: Add automatic backporting to staging for deployment workflows#132
crispy101 merged 2 commits intomainfrom
feature/DO-2013_auto_backporting_to_staging

Conversation

@crispy101
Copy link
Copy Markdown
Contributor

Add backport action that creates PRs to backport changes from production-like branches (production, main, master) to staging after successful deployments.

Changes:

  • Add .github/actions/backport/action.yml with source branch validation
  • Integrate backport step into all 9 deployment workflows
  • Update documentation for all affected workflows

Configuration:

  • BACKPORT_TO_STAGING=true to enable (repo or environment variable)
  • BACKPORT_TARGET_BRANCH to customize target (defaults to staging)

🤖 Generated with Claude Code

Description of the proposed changes

Screenshots (if applicable)

Other solutions considered (if any)

Notes to PR author

⚠️ Please make sure the changes adhere to the guidelines mentioned in our contribution guide.

Notes to reviewers

ℹ️ When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback

@crispy101 crispy101 requested a review from a team as a code owner April 15, 2026 04:08
Add backport action that creates PRs to backport changes from production-like
branches (production, main, master) to staging after successful deployments.

Changes:
- Add .github/actions/backport/action.yml with source branch validation
- Integrate backport step into all 9 deployment workflows
- Update documentation for all affected workflows

Configuration:
- BACKPORT_TO_STAGING=true to enable (repo or environment variable)
- BACKPORT_TARGET_BRANCH to customize target (defaults to staging)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@crispy101 crispy101 force-pushed the feature/DO-2013_auto_backporting_to_staging branch from 08cda05 to 26dbbb7 Compare April 15, 2026 04:11
@crispy101 crispy101 requested a review from TheOrangePuff April 15, 2026 04:11
Copy link
Copy Markdown
Contributor

@AdamJHall AdamJHall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to add the BACKPORT_TO_STAGING and BACKPORT_TARGET_BRANCH as inputs to each of the workflows? I don't think vars will get inherited with being explicitly added as inputs.

Comment thread docs/aio-app-deployment.md Outdated
@crispy101
Copy link
Copy Markdown
Contributor Author

Do we need to add the BACKPORT_TO_STAGING and BACKPORT_TARGET_BRANCH as inputs to each of the workflows? I don't think vars will get inherited with being explicitly added as inputs.

Thanks for picking this up. Updated.

@crispy101 crispy101 requested a review from AdamJHall April 15, 2026 06:32
Copy link
Copy Markdown

@tmthrgd-aligent tmthrgd-aligent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just a few questions, but none that are blocking.

Comment thread .github/actions/backport/action.yml
Comment thread .github/workflows/aio-app-deployment.yml
@crispy101 crispy101 merged commit fc49364 into main Apr 15, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants