fix send correct repo name in setstatus reporting

[motatoes]

• set correct status when sending repo in set-status endpoint
• set common logic in func

Summary by CodeRabbit

• Code Improvements

  • Updated repository name handling in backend reporting
  • Renamed method parameter for improved clarity
  • Simplified repository name construction for API requests

• Technical Updates

  • Modified how repository names are processed and reported
  • Streamlined backend API interaction logic

[coderabbitai]

Walkthrough

The pull request introduces changes to how repository names are processed and reported in the Digger CLI and backend API. The modifications primarily affect the ReportProjectJobStatus method across multiple files, focusing on how repository names are constructed and used when reporting job statuses. The changes simplify the repository name handling by directly using the repository name and introducing a consistent method of replacing slashes with hyphens for backend reporting.

Changes

File	Change Summary
cli/pkg/digger/digger.go	Removed slash replacement for namespace in job reporting
cli/pkg/spec/spec.go	Simplified repository name reporting by directly using spec.VCS.RepoName
libs/backendapi/diggerapi.go	Renamed repo parameter to repoFullName, added logic to replace "/" with "-" for backend reporting

Poem

🐰 A Digger's Tale of Names So Neat
Slashes dance and hyphens meet
Repository paths now streamlined bright
Backend reporting takes its flight
With clarity and code so sweet! 🚀

---

📜 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 de0a222 and 0f9b7cf.

📒 Files selected for processing (3)

• cli/pkg/digger/digger.go (1 hunks)
• cli/pkg/spec/spec.go (1 hunks)
• libs/backendapi/diggerapi.go (3 hunks)

🔇 Additional comments (5)

cli/pkg/spec/spec.go (1)

140-140: LGTM! The repository name handling is now consistent.

The change correctly uses spec.VCS.RepoName for status reporting, which aligns with the PR's objective of fixing repository name reporting.

libs/backendapi/diggerapi.go (3)

18-18: LGTM! Required import for string manipulation.

The addition of the strings package is necessary for the ReplaceAll function used in repository name formatting.

---

133-134: LGTM! Improved parameter naming and repository name formatting.

The changes enhance clarity and consistency:

1. Renamed parameter from repo to repoFullName for better clarity.
2. Added consistent formatting of repository names by replacing "/" with "-".

---

157-157: LGTM! Consistent use of formatted repository name.

The formatted repository name is correctly used in the API endpoint path construction.

cli/pkg/digger/digger.go (1)

145-145: LGTM! Simplified repository name handling.

The change correctly delegates the repository name formatting responsibility to the backend API by directly passing currentJob.Namespace.

Finishing Touches

• 📝 Generate Docstrings

---

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.