fix: run CI on v1 branch

[MuncleUscles]

Summary

Updates workflows that still filtered on retired main so they run against the current stable v1 branch.

• test.yml: push and PR branch filters now target v1.
• chains-drift.yml: push and PR branch filters now target v1.

Publish and docs-sync release flows were already tag/release based and are unchanged.

Verification

• git diff --check
• Parsed changed workflow YAML with yq e '.'

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow triggers to run on a specific branch instead of the default branch, affecting automated testing and integration processes.

[coderabbitai]

Warning

Rate limit exceeded

@MuncleUscles has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 54 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 984dcda9-8477-45ff-b0aa-304439051751

📥 Commits

Reviewing files that changed from the base of the PR and between f23fa8d and 7e4072e.

📒 Files selected for processing (2)

• src/chains/testnetAsimov.ts
• src/chains/testnetBradbury.ts

📝 Walkthrough

Walkthrough

This PR updates two GitHub Actions workflows to trigger on the v1 branch instead of main for both pull_request and push events. All other workflow configuration remains unchanged.

Changes

CI Workflow Branch Configuration

Layer / File(s)	Summary
Workflow trigger branch updates .github/workflows/chains-drift.yml, .github/workflows/test.yml	Both chains-drift and test workflows are reconfigured to trigger on the v1 branch instead of main for pull_request and push events.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit hops down the branch path,
From main to v1 so swift,
Both workflows now dance to the tune,
Of changes that gently drift,
CI runs free on the new way! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating CI workflows to run on the v1 branch instead of the retired main branch.
Description check	✅ Passed	The description covers the main changes and verification steps, though it omits some template sections like 'Why', 'Testing done', and 'Decisions made'.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/v1-ci-triggers

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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