ci: Improve build.yml

[warnyul]

• Change fetch-depth to 0 in release job
• Release job enabled only on the default branch
• Kover skipped on fork PRs

Summary by CodeRabbit

• Chores
  • Updated build workflow conditions for improved accuracy and performance.

[coderabbitai]

Walkthrough

The updates to the GitHub Actions workflow enhance the build process by adding more precise conditions for job execution and improving the checkout step's depth handling. These changes ensure that jobs only run on the default branch and for a specific repository, while also fetching the complete history during the checkout.

Changes

File	Change Summary
.github/workflows/build.yml	Updated job condition to check github.ref_name against default branch.
.../workflows/build.yml	Added fetch-depth: 0 to actions/checkout step.
.../workflows/build.yml	Included repository name check for 'apter-tech/junit5-robolectric-extension'.

🐰
In the land of code, where workflows flow,
A rabbit tweaks what makes it grow.
With branches checked and depths unfurled,
Our builds now dance in a smoother world.
🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Branch Coverage

Total Project Coverage	66.67%	✅

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9fffee5 and 74884bc.

Files selected for processing (1)

• .github/workflows/build.yml (2 hunks)

Additional comments not posted (3)

.github/workflows/build.yml (3)

73-73: Conditionally run the release job on the default branch with a non-SNAPSHOT version.

This condition ensures that the release job only runs on the default branch, during a manual dispatch event, and with a valid release version. This is a good practice to prevent accidental releases from non-default branches or with invalid versions.

---

76-77: Ensure full history is fetched for the release job.

Adding fetch-depth: 0 ensures that the entire Git history is fetched, which is necessary for creating accurate release tags and changelogs.

---

97-97: Conditionally run the kover job for pull requests in the main repository.

This condition ensures that the kover job only runs for pull requests in the main repository, preventing unnecessary runs on forked repositories. This is a good practice to save resources.

[github-actions]

Line Coverage

Total Project Coverage	83.95%	✅