♻️ refactor: fix and update make file

[tienld-0801]

🚀 Description

🔄 Type of Change

• ✨ feat: A new feature
• 🐛 fix: A bug fix
• 📚 docs: Documentation only changes
• 🎨 style: Changes that do not affect the meaning of the code
• ♻️ refactor: A code change that neither fixes a bug nor adds a feature
• ⚡ perf: A code change that improves performance
• 🧪 test: Adding missing tests or correcting existing tests
• 🔧 build: Changes that affect the build system or external dependencies
• 🔄 ci: Changes to our CI configuration files and scripts
• 🏠 chore: Other changes that don't modify src or test files

📝 Changes Made

🧪 Testing

• Tests pass locally
• New tests added for new functionality
• Existing tests updated as needed
• Manual testing completed

Test Results

📖 Documentation

• README updated if needed
• CHANGELOG.md updated
• Code comments added/updated
• API documentation updated

🔗 Related Issues

Fixes #
Closes #
Related to #

📸 Screenshots/Examples

✅ Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

🎯 Focus Areas for Review

🚨 Breaking Changes

📝 Additional Notes

---

Please ensure all checks pass before requesting review

Summary by CodeRabbit

• New Features

  • Expanded command targets: install/uninstall, Docker image build, release workflows (release/quick-release/dev-release/hotfix/revert/status/validate), Git hooks management, project branch setup, version info, emoji test, markdown lint, clean/clean-examples, and framework tests (React/Vue/all).

• Improvements

  • Richer release and version status outputs; enhanced security check/report with better fallbacks; markdown lint now auto-falls back to alternate runners.
  • Streamlined help/entry points; removed default target.

• Tests

  • Added targets to validate React/Vue project generation and a combined test-all.

• Chores

  • Reorganized and standardized public targets; trimmed target descriptions.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The Makefile removes build metadata and the default target, restructures existing targets, and adds many new ones for release workflows, Git hooks, Docker, security checks, markdown linting, testing, install/uninstall, cleaning, and version reporting. Release and revert flows are updated, including OS-aware edits to a Go constants file.

Changes

Cohort / File(s)	Summary
Metadata cleanup Makefile	Removed VERSION, BUILD_DATE, GIT_COMMIT, and LDFLAGS definitions.
Target surface reorg Makefile	Dropped default. Stripped descriptive suffixes from many targets (help, dev, run, demo, build, lint, test, etc.).
Release workflow Makefile	Added release, quick-release, dev-release, hotfix, revert-release, check-release, release-status, validate-release, version-info. Orchestrates pre-checks, hooks, external script; enhanced status/info output.
Revert/version editing Makefile, pkg/constants/constants.go	revert-release updates Go constants via OS-aware sed. Version info reports git commit/binary version.
Git hooks management Makefile, .git/hooks...	Added hooks (alias), install-hooks, uninstall-hooks, check-hooks, validate-commits.
Security tooling Makefile	security-check retained with better missing-tool messaging; added security-report under a Security section.
Markdown linting Makefile	markdown-lint now falls back to markdownlint-cli2 or npx.
Testing targets Makefile	Added test-react, test-vue, test-all; adjusted run to depend on test lint markdown-lint.
Build/run/docker Makefile	Added docker image build target; retained build, dev, run, demo with updated signatures.
Install/cleanup Makefile	Added install, uninstall, clean, clean-examples.
Project helpers Makefile	Added init-branches.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant MK as Makefile
  participant GH as Git Hooks
  participant RS as Release Script
  participant GT as Git

  Dev->>MK: make release
  activate MK
  MK->>GH: check/install hooks
  GH-->>MK: hooks ready
  MK->>GT: check-release (branch, status, tags, commits)
  GT-->>MK: status details
  alt pre-checks pass
    MK->>RS: invoke external release script
    RS-->>MK: release tag/version output
    MK-->>Dev: release complete
  else pre-checks fail
    MK-->>Dev: abort with status details
  end
  deactivate MK

Loading

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant MK as Makefile
  participant FS as File System
  participant SE as sed (OS-aware)
  participant GT as Git

  Dev->>MK: make revert-release
  activate MK
  MK->>FS: locate pkg/constants/constants.go
  MK->>SE: apply version revert substitution
  SE-->>MK: file updated
  MK->>GT: commit revert changes
  GT-->>MK: commit hash
  MK-->>Dev: revert complete
  deactivate MK

Loading

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant MK as Makefile
  participant L1 as markdownlint-cli2
  participant NPX as npx
  participant SEC as gosec

  Dev->>MK: make markdown-lint
  alt cli2 available
    MK->>L1: run lint
  else fallback
    MK->>NPX: run markdownlint-cli2 via npx
  end
  Dev->>MK: make security-check
  alt gosec installed
    MK->>SEC: run analysis
  else missing tool
    MK-->>Dev: instruct to install gosec
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~30 minutes

Poem

I thump my paws on targets new,
Hooks are set, the tags accrue;
Sed tiptoes through constants’ glade,
Releases bloom where checks were made.
Lints and tests in tidy rows—
A Docker burrow softly grows.
Hop! Ship! Another carrot glows.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• 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 ee440bc and 95261ea.

📒 Files selected for processing (1)

• Makefile (10 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch reactorrefactor/remove-command-and-update-makefile

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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]

✅ Commit Validation Passed

All commits follow the conventional commit format! 🎉

Thank you for following our commit standards. This helps with:

• 📝 Automated changelog generation
• 🏷️ Automatic PR labeling
• 🚀 Better release notes
• 📊 Project history tracking

[github-actions]

🚨 Emergency Labeling Applied

This PR was automatically labeled as "❓ Needs Review" because no other labels could be applied.

Please:

1. Update the PR title to follow conventional commit format
2. Or manually apply appropriate labels

This ensures proper organization and searchability of PRs.

[github-actions]

🚨 Emergency Labeling Applied

This PR was automatically labeled as "❓ Needs Review" because no other labels could be applied.

Please:

1. Update the PR title to follow conventional commit format
2. Or manually apply appropriate labels

This ensures proper organization and searchability of PRs.