fix(publish_release): allow ci workflow to push to main

[saltenasl]

Summary by CodeRabbit

• Chores
  • Streamlined development workflow by optimizing pre-push verification in continuous integration environments while maintaining existing branch protection safeguards.

[coderabbitai]

📝 Walkthrough

Walkthrough

The .husky/pre-push hook script is modified to exit early when a CI environment is detected, bypassing subsequent checks. The existing guard preventing main-branch pushes is retained but now executes only in non-CI environments. The CI detection occurs before branch-name validation in the execution flow.

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "fix(publish_release): allow ci workflow to push to main" directly corresponds to the main change in the changeset. The raw summary confirms that the modification adds a CI environment detection that skips the pre-push hook, effectively bypassing the guard preventing pushes to main during CI runs. The title is specific, clear, and accurately reflects the primary objective without being vague or overly broad.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between acdfd73 and 906e9ed.

📒 Files selected for processing (1)

• .husky/pre-push (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: check_release
• GitHub Check: build

🔇 Additional comments (1)

.husky/pre-push (1)

1-5: Verify branch protection is configured; consider restricting to specific workflow.

GitHub Actions sets CI=true in runner environments, so the bypass works correctly there. However, the check allows any CI system to bypass—if only your release workflow should push to main, verify branch protection rules are configured, or use $GITHUB_WORKFLOW == 'release' for stricter isolation.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.56%. Comparing base (acdfd73) to head (906e9ed).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #61   +/-   ##
=======================================
  Coverage   69.56%   69.56%           
=======================================
  Files          13       13           
  Lines         253      253           
  Branches       28       28           
=======================================
  Hits          176      176           
  Misses         73       73           
  Partials        4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.