fix(ci): broken CI/CD

[tankerkiller125]

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow to use ${{ github.sha }} for BUILD_TIME and COMMIT variables.
  • Removed the BUILD_TIME variable from the Docker publish workflow.
  • Minor formatting improvements in the workflow files.

[coderabbitai]

Warning

Rate limit exceeded

@tankerkiller125 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 51 minutes and 26 seconds before requesting another review.

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.

Commits

Files that changed from the base of the PR and between 1cdf2c7 and 5e5a12f.

Walkthrough

The overall changes primarily focus on refining the variable assignments within two GitHub Actions workflow files. The BUILD_TIME and COMMIT variables are updated to more efficiently use ${{ github.sha }} for consistency and reliability. Additionally, minor formatting adjustments have been made to ensure clarity. These changes enhance the automation process, ensuring it is more straightforward and dependable.

Changes

Files	Change Summaries
.github/workflows/docker-publish-rootless.yaml	Modified BUILD_TIME to use ${{ github.sha }}. Minor formatting in push-to-registry.
.github/workflows/docker-publish.yaml	Removed the BUILD_TIME variable. Updated COMMIT to use ${{ github.sha }}.

Poem

In code's vast expanse, a tweak so grand,
Variables refined by meticulous hand.
SHA-1 commits now take their place,
Ensuring builds with elegant grace.
Formatting clear, workflows in tune,
Automation sings a streamlined tune.
Small changes made, efficiencies bloom,
In CI/CD, no room for gloom. 🌟

---

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a3f4c97 and 1cdf2c7.

Files selected for processing (2)

• .github/workflows/docker-publish-rootless.yaml (2 hunks)
• .github/workflows/docker-publish.yaml (2 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/docker-publish.yaml

Additional comments not posted (1)

.github/workflows/docker-publish-rootless.yaml (1)

100-100: Ensure clarity in the push-to-registry step.

The push-to-registry step's formatting and placement are crucial for understanding at a glance what conditions lead to pushing. This line appears to be well-placed and follows the logical flow of the job, ensuring that the image is pushed only when it's not a pull request, which aligns with the best practices of CI/CD pipelines.