Adopt the unified sc deploy workflow #22
Loading…
Reference in a new issue
No description provided.
Delete branch "claude/adopt-unified-sc-workflow"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replaces pr-environment.yml, staging.yml and production.yml with a single deploy.yml that infers mode and deployment from the trigger instead of hardcoding it per file. Same three environments (PR previews, staging tracking main, production tracking the prod tag) plus branch-named deployments for anything else, all from one job.
See https://git.grey.ooo/Grey.ooo/someones.computer_pr-environment-action for the resolution rules and the deployment-report PR comment this now also posts.
@main doesn't have the auto-detected mode/deployment logic yet — the push that just landed on this branch hit the old resolve step's hard error ("no deployment name given ... pass 'deployment' explicitly"), and the pull_request run silently deployed nothing (mode was never 'up' since nothing sets it without the inference). Pinning to the commit that has the fix until it merges. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.