Feature/697 feature add command to reanalyze commit in codacy

[guibranco]

Closes #

📑 Description

✅ Checks

• [ ] My pull request adheres to the code style of this project
• [ ] My code requires changes to the documentation
• [ ] I have updated the documentation as required
• [ ] All the tests have passed

☢️ Does this introduce a breaking change?

• [ ] Yes
• [ ] No

ℹ Additional Information

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced commands for the GStraccini-bot: @gstraccini codacy bypass and @gstraccini codacy reanalyze commit.
  • Added functionality to reanalyze commits in Codacy, enhancing user experience with GitHub comments and reactions.

• Bug Fixes

  • Improved error logging for the bypass analysis function, providing clearer feedback.

• Documentation

  • Updated README.md to reflect new commands available for users.

[coderabbitai[bot]]

[!CAUTION]

Review failed

The pull request is closed.

Walkthrough

This pull request introduces updates to enhance the GStraccini-bot's integration with Codacy and simplify the commit message generation process. The .githooks/prepare-commit-msg script has been streamlined by removing unnecessary variables and clarifying existing ones. The README.md file now includes new commands for bypassing and reanalyzing Codacy analysis. Additionally, new functions are implemented in Src/comments.php and Src/lib/codacy.php to support commit reanalysis, along with a new command defined in Src/config/commands.json.

Changes

File	Change Summary
.githooks/prepare-commit-msg	Removed GIT_DIFF variable and branch name retrieval; renamed CURRENT to CURRENT_MESSAGE; simplified AI message generation command.
README.md	Added commands: @gstraccini codacy bypass and @gstraccini codacy reanalyze commit.
Src/comments.php	Added function execute_codacyReanalyzeCommit for reanalyzing a commit in Codacy; modified execute_createLabels for better logging.
Src/config/commands.json	Added command entry for "codacy reanalyze commit" with description and requirement for open pull request.
Src/lib/codacy.php	Added function reanalyzeCommit for sending reanalysis requests to Codacy; modified error logging in bypassPullRequestAnalysis.

Possibly related issues

• guibranco/gstraccini-bot-service#697: This issue requests the addition of a command to reanalyze commits in Codacy, which is directly addressed by the new command @gstraccini codacy reanalyze commit introduced in this PR.

Possibly related PRs

• #613: Involves changes to the .githooks/prepare-commit-msg script, relevant to the modifications made in this PR.
• #620: Modifies Src/comments.php, which is relevant due to potential interactions with commit message processing.
• #626: Updates Src/comments.php, enhancing user feedback that may relate to commit message generation.
• #633: Introduces command execution functions in Src/comments.php, possibly interacting with commit message generation.
• #641: Modifies execute_createLabels in Src/comments.php, which could relate to commit message processing.
• #645: Updates handleItem in Src/comments.php, potentially interacting with commit message generation.

Suggested reviewers

• gstraccini: Suggested reviewer for expertise in GStraccini-bot development.

Poem

🐰 In the meadow where code does play,
A new command hops in today!
With Codacy's help, we'll analyze,
Commit messages, oh what a prize!
Bypass or reanalyze with ease,
GStraccini-bot, you aim to please! 🌼

[!WARNING]

Rate limit exceeded

@guibranco has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 14 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 48cd1ef34f95751e0e93bbe1b92c849a402d3cd2 and 85086fa130496be0f2e1536033564d44262694fb.

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[deepsource-io[bot]]

Here's the code health analysis summary for commits 48cd1ef..85086fa. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Docker	✅ Success		View Check ↗
PHP	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
SQL	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[sonarcloud[bot]]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions[bot]]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

```txt 11:44PM INF scanning for exposed secrets... 11:44PM INF 645 commits scanned. 11:44PM INF scan completed in 147ms 11:44PM INF no leaks found ```

[guibranco]

@gstraccini codacy bypass

[gstraccini[bot]]

Bypassing the Codacy analysis for this pull request! :warning: