Skip to content

chore: point branch references at main after multicloud->main merge#1132

Merged
cristim merged 1 commit into
mainfrom
docs/retire-multicloud-branch-ref
Jun 9, 2026
Merged

chore: point branch references at main after multicloud->main merge#1132
cristim merged 1 commit into
mainfrom
docs/retire-multicloud-branch-ref

Conversation

@cristim

@cristim cristim commented Jun 9, 2026

Copy link
Copy Markdown
Member

Summary

feat/multicloud-web-frontend was merged into main via PR #1131 and the branch is now retired. This PR removes all forward-looking/operational references to it so the repo correctly reflects main as the sole integration base.

Files changed

File Reference New value
.github/workflows/deploy-aws-lambda.yml branches: [main, feat/multicloud-web-frontend] push trigger + comment header branches: [main] / updated comment
.github/workflows/deploy-azure.yml branches: [main, feat/multicloud-web-frontend] push trigger + comment header branches: [main] / updated comment
.github/workflows/deploy-gcp.yml branches: [main, feat/multicloud-web-frontend] push trigger + comment header branches: [main] / updated comment
.github/workflows/pre-commit.yml branches: [main, feat/multicloud-web-frontend] on both pull_request and push triggers branches: [main] on both
.github/workflows/frontend-build.yml - feat/multicloud-web-frontend in pull_request.branches list removed (only main remains)
terraform/environments/azure/ci-cd-permissions/sp.tf azuread_application_federated_identity_credential.github_feat_multicloud resource binding OIDC subject refs/heads/feat/multicloud-web-frontend resource removed (branch no longer exists)
README.md "part of the feat/multicloud-web-frontend branch and is not yet merged to main" "included in main"

Historical references left in place

These describe past events and were intentionally not changed:

  • frontend/src/recommendations.ts:140 — code comment recording that a verification was performed against origin/feat/multicloud-web-frontend
  • specs/migration-resilience.md:161 — records the branch a specific commit was introduced on

Test plan

  • Confirm grep -rn "feat/multicloud-web-frontend" . --exclude-dir=.git returns only the two historical lines listed above
  • All 5 edited workflow YAML files parse without error
  • Deploy workflows now trigger only on main pushes
  • pre-commit and frontend-build workflows now filter only main
  • Terraform plan for terraform/environments/azure/ci-cd-permissions/ shows destruction of azuread_application_federated_identity_credential.github_feat_multicloud[0] only

feat/multicloud-web-frontend has been merged into main (PR #1131) and
retired. Update every forward-looking/operational reference so the repo
reflects main as the sole integration base.

Changes:
- .github/workflows/deploy-{aws-lambda,azure,gcp}.yml: remove retired
  branch from push trigger branches list and update comment header
- .github/workflows/pre-commit.yml: remove retired branch from both
  pull_request and push branch filters
- .github/workflows/frontend-build.yml: remove retired branch from
  pull_request branch filter
- terraform/environments/azure/ci-cd-permissions/sp.tf: remove the
  github_feat_multicloud federated identity credential resource (the
  OIDC subject it bound, refs/heads/feat/multicloud-web-frontend, no
  longer exists)
- README.md: replace "part of feat/multicloud-web-frontend and not yet
  merged to main" with "included in main"

Historical references left in place (describing past events):
- frontend/src/recommendations.ts:140 - code comment recording which
  branch a verification was performed on ("verified against the
  recommendation collectors on origin/feat/multicloud-web-frontend")
- specs/migration-resilience.md:161 - records the branch a specific
  commit was introduced on ("branch feat/multicloud-web-frontend")
@cristim cristim added triaged Item has been triaged priority/p2 Backlog-worthy effort/s Hours type/chore Maintenance / non-user-visible labels Jun 9, 2026
@cristim

cristim commented Jun 9, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@cristim, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 39 minutes and 28 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c9ce7254-ef13-4ed1-878a-75f399a64588

📥 Commits

Reviewing files that changed from the base of the PR and between 3445821 and 4f7d429.

📒 Files selected for processing (7)
  • .github/workflows/deploy-aws-lambda.yml
  • .github/workflows/deploy-azure.yml
  • .github/workflows/deploy-gcp.yml
  • .github/workflows/frontend-build.yml
  • .github/workflows/pre-commit.yml
  • README.md
  • terraform/environments/azure/ci-cd-permissions/sp.tf
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/retire-multicloud-branch-ref

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@cristim cristim merged commit 8378214 into main Jun 9, 2026
9 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

effort/s Hours priority/p2 Backlog-worthy triaged Item has been triaged type/chore Maintenance / non-user-visible

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant