GitAuto: [BUG] Check if actions requested to checkout the repository are not in a external pull request

[gitauto-ai]

Resolves #93

Why the bug occurs

When the bot processes the @gstraccini csharpier command on a pull request, it attempts to checkout the PR branch from the original repository without considering whether the PR originates from a forked repository. If the PR comes from a fork, the bot doesn't have the necessary permissions to access the forked repository, causing the checkout action to fail. The bot doesn't provide any feedback to the user about this failure, leading to confusion.

How to reproduce

1. Submit a pull request from a forked repository to the original repository.
2. Comment @gstraccini csharpier on the PR.
3. Observe that the bot tries to checkout the PR branch from the original repository instead of the fork.
4. The action fails silently without informing the user of the issue.

How to fix

Modify the bot's workflow to detect if a PR originates from a forked repository. If it does, the bot should:

1. Avoid attempting to checkout the code from the forked repository, as it doesn't have the necessary permissions.
2. Post a comment on the PR explaining that it cannot perform the action due to permission restrictions.

Implementation Steps:

1. Check if the PR is from a fork:

   In the GitHub Actions workflow handling the @gstraccini csharpier command, add a step to determine if the PR is from a forked repository by checking the github.event.pull_request.head.repo.fork property.

   - name: Check if PR is from a fork
     id: check_fork
     run: echo "isFork=${{ github.event.pull_request.head.repo.fork }}" >> $GITHUB_OUTPUT

2. Conditionally perform actions based on the fork status:

   Update the workflow to only attempt to checkout and run actions if the PR is not from a fork.

   - name: Checkout code
     if: steps.check_fork.outputs.isFork == 'false'
     uses: actions/checkout@v3
     with:
       repository: ${{ github.event.pull_request.head.repo.full_name }}
       ref: ${{ github.event.pull_request.head.ref }}
   
   - name: Run CSharpier
     if: steps.check_fork.outputs.isFork == 'false'
     run: |
       # Commands to run CSharpier

3. Comment on the PR if it is from a fork:

   If the PR is from a forked repository, use the actions/github-script action to post a comment informing the user.

   - name: Comment on PR
     if: steps.check_fork.outputs.isFork == 'true'
     uses: actions/github-script@v6
     with:
       script: |
         github.rest.issues.createComment({
           owner: context.repo.owner,
           repo: context.repo.repo,
           issue_number: context.issue.number,
           body: '⚠️ Sorry, I cannot perform this action on pull requests from forked repositories due to permission restrictions.'
         })

By implementing these changes, the bot will properly handle PRs from forked repositories by notifying users of the permission limitations instead of failing silently. This improves user experience by providing clear feedback and avoids unnecessary action failures.

Test these changes locally

git checkout -b gitauto/issue-#93-847f959d-c860-4505-8d6e-d39e533f2012
git pull origin gitauto/issue-#93-847f959d-c860-4505-8d6e-d39e533f2012

[deepsource-io]

Here's the code health analysis summary for commits 7f7cf9e..87a6943. 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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 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.

[sonarcloud]

Quality Gate passed

Issues
0 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]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

5:40PM INF scanning for exposed secrets...
5:40PM INF 650 commits scanned.
5:40PM INF scan completed in 146ms
5:40PM INF no leaks found