You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: deploy HappyView modules to test on push to main - #62
Adds a Test deploy: every push to main now installs the HappyView modules into the test HappyView via the Test GitHub environment, alongside Staging and Production.
Changes
deploy.yml also triggers on main. A small resolve job maps branches to environments explicitly (main→Test, staging→Staging, production→Production) and fails on unmapped branches.
Concurrency is per environment, never cancelled midway. Still --override, contents: read, SHA-pinned actions.
happyview-modules/README.md Deploys section lists all three environments and their required settings.
Rollout
Before merging, the Test environment needs HAPPYVIEW_BASE_URL, HAPPYVIEW_ADMIN_TOKEN (and HYPERCERTS_HANDLE_RESOLVER_URL if the test HappyView lacks it), and must allow deployments from main. Otherwise the merge's own deploy fails.
Summary by CodeRabbit
Deployment
Deployments now run from main, staging, and production, targeting the corresponding Test, Staging, and Production environments.
Deployments are serialized within each environment, while deployments to different environments can proceed independently.
Documentation
Updated deployment guidance with the branch-to-environment mapping and environment-specific token requirements.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
No actionable comments were generated in the recent review.
Walkthrough
The deployment workflow now runs on main, staging, and production. It maps each branch to a GitHub environment and scopes deployment concurrency to that environment. The README describes the mappings, token guidance, and concurrency behavior.
Changes: Environment-scoped deployments
Layer / File(s)
Summary
Branch mapping and deployment .github/workflows/deploy.yml, happyview-modules/README.md
The workflow maps main, staging, and production to Test, Staging, and Production. The deploy job uses the mapped environment and groups concurrency by environment without cancelling in-progress deployments. The README documents the branch mappings, token guidance, and concurrency behavior.
hypercerts-org/api#60: Adds a separate production deployment workflow and updates the same deployment documentation.
Suggested reviewers:kristoferlund
Merge Risk: Minimal · up to fd80f
This change adds a Test deployment on pushes to main and documents it. The Test GitHub environment must be configured with its required settings, or the first deploy after merge will fail. No code-level merge blockers were found.
Pre-merge checks: 4
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title names the main change: a Test deployment of HappyView modules triggered by pushes to main. The raw summary confirms the deploy workflow now maps main to the Test environment via a resolve jo…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Title check
Explanation
The title names the main change: a Test deployment of HappyView modules triggered by pushes to main. The raw summary confirms the deploy workflow now maps main to the Test environment via a resolve job, and the README was updated to match. The title uses the conventional-commit prefix ci:, which fits a workflow change. It does not mention the explicit branch-to-environment mapping or the concurrency change, but those are secondary details.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: d946d87d-c43c-460c-84b9-30922a50f5e1
Commits
Reviewing files that changed from the base of the PR and between 8d5c2d1 and fd80fb9.
Files selected for processing: 2
.github/workflows/deploy.yml
happyview-modules/README.md
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Test deploy: every push to
mainnow installs the HappyView modules into the test HappyView via theTestGitHub environment, alongside Staging and Production.Changes
deploy.ymlalso triggers onmain. A smallresolvejob maps branches to environments explicitly (main→Test,staging→Staging,production→Production) and fails on unmapped branches.--override,contents: read, SHA-pinned actions.happyview-modules/README.mdDeploys section lists all three environments and their required settings.Rollout
Before merging, the
Testenvironment needsHAPPYVIEW_BASE_URL,HAPPYVIEW_ADMIN_TOKEN(andHYPERCERTS_HANDLE_RESOLVER_URLif the test HappyView lacks it), and must allow deployments frommain. Otherwise the merge's own deploy fails.Summary by CodeRabbit
main,staging, andproduction, targeting the corresponding Test, Staging, and Production environments.