GITHUB_ACCESS_TOKEN to ACCESS_TOKEN_GITHUB

[ManiShankarCdAnt]

CodeAnt-AI Description

Use ACCESS_TOKEN_GITHUB secret name in README workflow examples

What Changed

• Workflow examples in the README now use secrets.ACCESS_TOKEN_GITHUB for the action's access_token instead of secrets.GITHUB_ACCESS_TOKEN.
• Setup instructions were updated to tell users to create a repository secret named ACCESS_TOKEN_GITHUB.
• Troubleshooting wording now refers to ACCESS_TOKEN_GITHUB when checking authentication token validity.

Impact

✅ Fewer authentication failures when uploading coverage
✅ Shorter setup time by following correct copy-paste workflow
✅ Clearer secret naming so users create the correct repository secret

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[codeant-ai]

Pull Request Feedback 🔍

🔒 No security issues identified

⚡ Recommended areas for review Documentation Mismatch The usage examples show access_token: ${{ secrets.ACCESS_TOKEN_GITHUB }}, but the Inputs table does not mention the expected repository secret name or recommended scopes. Ensure the Inputs or Setup sections consistently reference the example secret name and clarify expected token scopes/permissions.

[codeant-ai]

Suggestion: Replace the single-line authentication note with a short, actionable paragraph listing the minimal required token scopes (e.g., repo for private repos, public_repo for public repos) and mention workflow-related scopes if applicable. [best practice]

[codeant-ai]

Suggestion: Clarify that ACCESS_TOKEN_GITHUB is a CodeAnt AI access token (not the runner-provided GITHUB_TOKEN) by expanding the line to explicitly state this to avoid user confusion. [best practice]

[codeant-ai]

CodeAnt AI finished reviewing your PR.