Tag option for super easy deployment

[statefb]

@claude Make some edits to make it possible to deploy this solution by using bin.sh with git tag option like --tag v1.0.0

[claude]

Claude finished @statefb's task —— View job • claude/issue-22-20250624_015650 • Create PR ➔

---

Todo List

• Create a plan and checklist for implementation
• Gather context from repository - check CLAUDE.md and related files
• Inspect bin.sh to understand current deployment process
• Implement git tag option in deployment script
• Test the changes locally
• Update documentation if needed
• Commit changes and provide PR link

I've implemented the requested git tag option for the deployment process. Here's what I did:

1. Added a new --tag parameter to bin.sh that allows specifying a git tag for deployment
2. Updated deploy.yml to:
   • Add a new GitTag parameter
   • Add logic to clone and checkout the specified tag when provided
   • Pass the tag parameter to the CodeBuild project
3. Updated the documentation in README.md to include the new --tag option

With these changes, you can now deploy a specific git tag using:

./bin.sh --tag v1.0.0

When a tag is specified, it will take precedence over the branch parameter.

[statefb]

@claude if no tag option specified, how behave this deployment method?

[claude]

Claude finished @statefb's task —— View job

---

I'll analyze how the deployment method behaves when no tag option is specified.

Todo List

• Analyze the current implementation of bin.sh
• Understand how the deployment flow works
• Determine the default behavior when no tag option is specified

Based on my analysis of the code:

When no --tag option is specified, the deployment uses the branch-based approach that was originally implemented. Specifically:

1. The deployment script uses the --branch parameter (which defaults to "main" if not specified)
2. The CodeBuild project clones the repository using: git clone --branch $BRANCH $REPO_URL rapid
3. This means it will deploy the latest code from the specified branch (or "main" by default)

So the behavior without the tag option is:

• Deploy using branch name (default: "main")
• Use the latest commit from that branch
• Any changes merged to that branch since the last deployment will be included

The branch-based deployment remains fully backward compatible with existing usage patterns.