Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Aug 5, 2025

πŸš€ Integration from develop to staging

πŸ“Š Summary

  • Commits: 9 new commits
  • Created: 2025-08-05 10:20:35 UTC
  • Auto-generated: This PR was automatically created by the integration workflow

πŸ“ Recent Commits

  • fix: use existing labels in all workflows (12c5b8f)%0A- fix: resolve all YAML syntax errors in workflows (e8bb014)%0A- fix: correct heredoc syntax in integrate-develop workflow (9b5fb63)%0A- fix: resolve multi-line string issues in all workflows (fad2ac6)%0A- fix: resolve YAML syntax errors in integrate-develop workflow (7b2d90b)%0A- fix: handle staging branch fetch in integrate-develop workflow (5f7de1f)%0A- test: trigger integrate-develop workflow (c277ee4)%0A- fix: update workflow configurations (eb6d93d)%0A- feat: implement new Git Flow workflow strategy (f4416b0)

πŸ” What happens next?

  1. Review the changes in this PR
  2. Run any necessary QA tests
  3. When approved and merged, the staging workflow will:
    • Check for changesets
    • If found, create beta releases
    • Automatically create a PR to main

⚑ Notes

  • This PR will be automatically updated with new commits to develop
  • Multiple features can accumulate in this single PR\n\n### πŸ”„ Last Updated: 2025-08-05 10:23:14 UTC\nNew commits: 11\n\n### πŸ“ Recent Commits\n- revert: remove unnecessary changeset for workflows (a514355)%0A- chore: add changeset for workflow updates (549e470)%0A- fix: use existing labels in all workflows (12c5b8f)%0A- fix: resolve all YAML syntax errors in workflows (e8bb014)%0A- fix: correct heredoc syntax in integrate-develop workflow (9b5fb63)%0A- fix: resolve multi-line string issues in all workflows (fad2ac6)%0A- fix: resolve YAML syntax errors in integrate-develop workflow (7b2d90b)%0A- fix: handle staging branch fetch in integrate-develop workflow (5f7de1f)%0A- test: trigger integrate-develop workflow (c277ee4)%0A- fix: update workflow configurations (eb6d93d)%0A- feat: implement new Git Flow workflow strategy (f4416b0)

- Add integrate-develop.yml for automatic PR creation from develop to staging
- Add release-staging.yml for beta releases when changesets exist
- Add update-version.yml for version updates in main branch
- Add release-tag.yml for tag-based production releases
- Move old workflows to legacy folder
- Update RELEASE_STRATEGY.md and Korean version
- Create comprehensive Git Flow documentation

This new workflow implements:
- Automated PR creation: develop β†’ staging β†’ main
- Beta releases from staging with changesets
- Version updates in main without npm publish
- Tag-triggered production releases
- Automatic branch synchronization
- Fix beta tag passing in release-staging.yml to use RELEASE_TAG env var
- Add staging branch to pr-check.yml trigger branches
- Fix variable interpolation in multi-line strings
- Use shell variables instead of direct GitHub Actions expressions in PR body
- Fixed integrate-develop.yml: Use here-doc for PR body
- Fixed release-staging.yml: Use here-doc for PR body
- Fixed update-version.yml: Use here-doc for PR bodies
- Fixed release-tag.yml: Use here-doc for release notes

All workflows now properly handle multi-line strings with GitHub Actions expressions
- Split PR body creation to handle multi-line commits properly
- Avoid variable expansion issues in heredoc
- Remove test file
- Fixed integrate-develop.yml: Replace heredoc with echo commands to avoid YAML parsing conflicts
- Fixed update-version.yml: Replace heredoc blocks with echo commands
- All workflows now pass GitHub Actions YAML validation
- Verified with yaml-validator and GitHub CLI

This should stop the workflow error notification emails.
- Replace non-existent labels with existing ones
- integration -> auto-updated
- automated -> (removed)
- sync -> auto-updated
- release -> released
- beta -> (removed)

This fixes 'label not found' errors in PR creation
This ensures the new workflows reach main branch through the proper release process
Workflow changes don't need changesets
@github-actions github-actions bot changed the title πŸ”„ Integrate develop β†’ staging πŸ”„ Integrate develop β†’ staging (10 commits) Aug 5, 2025
@github-actions github-actions bot changed the title πŸ”„ Integrate develop β†’ staging (10 commits) πŸ”„ Integrate develop β†’ staging (11 commits) Aug 5, 2025
@Seungwoo321 Seungwoo321 merged commit bf58bae into staging Aug 5, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants