fix(ci): fixed project name for GHA

[COLDTURNIP]

This change corrects the image name for GHA, to decouple the name from build environment

[coderabbitai]

Walkthrough

The changes update the Makefile to ensure the IMAGE_NAME variable is properly set when invoking the dapper/package script. A new variable PROJECT is introduced with the value longhorn-cli, and two Makefile targets—workflow-image-build-push and workflow-image-build-push-secure—are modified to include IMAGE_NAME=$(PROJECT) in their command invocations.

Changes

File	Change Summary
Makefile	- Added PROJECT := longhorn-cli declaration. - Updated workflow-image-build-push target: command now includes IMAGE_NAME=$(PROJECT) before running bash dapper/package. - Updated workflow-image-build-push-secure target similarly, adding IMAGE_NAME=$(PROJECT) alongside IS_SECURE=true.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant M as Makefile
    participant D as dapper/package

    U->>M: Invoke workflow-image-build-push or workflow-image-build-push-secure
    M->>M: Set IMAGE_NAME = PROJECT (longhorn-cli)
    M->>D: Execute bash dapper/package with env vars (MACHINE, PUSH, [IS_SECURE])
    D-->>M: Return build result

Loading

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 58d5dba and db15ec7.

📒 Files selected for processing (1)

• Makefile (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build binaries
• GitHub Check: Summary

🔇 Additional comments (3)

Makefile (3)

1-1: Define PROJECT Variable Appropriately
The explicit definition of PROJECT := longhorn-cli cleanly decouples the project name from the build environment and improves clarity in the CI configuration.

---

30-31: Pass IMAGE_NAME in Workflow Target
The updated command in the workflow-image-build-push target now correctly includes IMAGE_NAME=$(PROJECT), ensuring that the image name reflects the intended project name when invoking the dapper packaging script.

---

32-33: Consistent Variable Usage in Secure Workflow
The secure build target (workflow-image-build-push-secure) now also properly passes IMAGE_NAME=$(PROJECT) along with IS_SECURE=true, maintaining consistency across build modes as outlined in the PR objectives.

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.