fix(ci): fixed project name for GHA

[COLDTURNIP]

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

Summary by CodeRabbit

• Chores
  • Improved the internal deployment pipeline by ensuring that all necessary variables for image packaging are explicitly included during the build process.

[coderabbitai]

Walkthrough

The pull request updates the Makefile by modifying the workflow-image-build-push and workflow-image-build-push-secure targets. The changes add the IMAGE_NAME=$(NAME) variable to the commands that execute the packaging script. This adjustment explicitly passes the image name to the script while leaving other variables and the overall flow intact.

Changes

File	Summary
Makefile	Updated the workflow-image-build-push and workflow-image-build-push-secure targets to pass IMAGE_NAME=$(NAME) to the packaging script.

Sequence Diagram(s)

sequenceDiagram
    participant User as Developer
    participant M as Makefile
    participant S as PackageScript
    User->>M: Invoke build-push target
    M->>S: Execute "bash scripts/package" with IMAGE_NAME, MACHINE, VERSION, etc.
    S-->>M: Return package status

Loading

Suggested reviewers

• derekbit

Poem

I'm a little rabbit, hopping with glee,
In the code garden, where changes are free.
IMAGE_NAME now leads the way,
Lighting up the build like a bright new day.
With each command, I bounce and play! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 50d09d1 and 6431bda.

📒 Files selected for processing (1)

• Makefile (1 hunks)

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

• GitHub Check: Summary

🔇 Additional comments (2)

Makefile (2)

35-35: Explicitly Passing IMAGE_NAME is Correct for Decoupling from Build Environment
The addition of IMAGE_NAME=$(NAME) explicitly passes the image name into the packaging script. This decouples it from any implicit environment dependency and ensures the correct project name is used in the CI/CD process.

---

37-37: Consistent Update for Secure Workflow Target
Similarly, in the secure build target, the inclusion of IMAGE_NAME=$(NAME) alongside IS_SECURE=true correctly aligns with the desired decoupling of the image name from the build environment. The consistency between both targets improves clarity and maintainability.

---

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.

CodeRabbit Configuration 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.

[derekbit]

LGTM