Allow find latest default

[a-magdy]

Remove a requirement on both find-latest & fetch-co-latest to have the regex be passed as an input
Instead default it to '*' if not provided

Summary by CodeRabbit

• Bug Fixes

  • Corrected a typo in error messages for improved clarity.

• New Features

  • The regex argument for tag filtering is now optional; if not provided, all tags are considered by default, and users are notified when this default is used.

[coderabbitai]

Walkthrough

The find-latest function was updated to explicitly scope tag filtering to refs/tags/ in the git ls-remote command. The error message typo was corrected. In the main function, the regex argument for tag filtering is now optional and defaults to "*" if unset, with a corresponding informational message.

Changes

Cohort / File(s)	Change Summary
find-latest tag filtering & error message git-artifact	Updated git ls-remote to use "refs/tags/${arg_regex}" for tag filtering; fixed typo in error message.
Main function argument handling git-artifact	Made the `-r

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MainFunction
    participant FindLatest

    User->>MainFunction: Run fetch-co-latest or find-latest
    MainFunction->>MainFunction: Check if regex argument is set
    alt Regex argument unset
        MainFunction->>User: Print info: defaulting regex to "*"
        MainFunction->>FindLatest: Call with regex="*"
    else Regex argument set
        MainFunction->>FindLatest: Call with provided regex
    end
    FindLatest->>FindLatest: Run git ls-remote with "refs/tags/${regex}"
    FindLatest-->>MainFunction: Return result or error
    MainFunction-->>User: Output result or error message

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Allow find latest default #22: Implements the same changes, including scoping tag filtering, correcting the typo, and making the regex argument optional.

Suggested reviewers

• bicschneider

Poem

A regex for tags, now clear and precise,
No more typos—our messages are nice!
If you forget the pattern, don’t worry or fret,
The default will catch every tag you can get.
🐇✨
Hopping through code with a bug-fixing cheer,
These changes bring clarity—let’s all give a cheer!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 a990c3c and 6f45f4f.

📒 Files selected for processing (1)

• git-artifact (2 hunks)

🔇 Additional comments (3)

git-artifact (3)

335-335: LGTM! Improved tag reference scoping.

The change to explicitly scope the regex pattern to refs/tags/ enhances precision and prevents potential issues where the regex might inadvertently match other reference types. This aligns well with the function's purpose of finding the latest tags.

---

339-339: LGTM! Typo correction.

Good catch on fixing the spelling error from "happend" to "happened" in the error message.

---

500-503: LGTM! Well-implemented optional regex with sensible defaults.

The implementation correctly handles the optional regex parameter by:

• Using proper bash parameter expansion ${arg_regex:-} to check for unset/empty values
• Defaulting to "*" which will match all tags when combined with the refs/tags/ prefix
• Providing clear user feedback through the informational message
• Maintaining backward compatibility while simplifying usage

This change successfully achieves the PR objective of making the regex parameter optional for both find-latest and fetch-co-latest commands.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.

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.