Skip to content

fix: trigger latest release to version 2#48

Merged
dev-davexoyinbo merged 1 commit into
mainfrom
v2
May 25, 2026
Merged

fix: trigger latest release to version 2#48
dev-davexoyinbo merged 1 commit into
mainfrom
v2

Conversation

@dev-davexoyinbo
Copy link
Copy Markdown
Contributor

No description provided.

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Fix typo in GitHub provider key in README

🐞 Bug fix

Grey Divider

Walkthroughs

Description
• Fix typo in GitHub provider key documentation
• Changed github to github. in README table
Diagram
flowchart LR
  README["README.md"] -- "Fix typo: github → github." --> DOCS["Documentation Update"]

Loading

File Changes

1. README.md 📝 Documentation +1/-1

Fix GitHub provider key typo

• Fixed typo in GitHub provider key from github to github. in the provider status table

README.md


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented May 25, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

Grey Divider


Action required

1. Wrong GitHub provider key 🐞 Bug ≡ Correctness
Description
README.md lists the GitHub provider key as github. but the module’s supported provider identifier
is github, so users copying the documented key will configure an unknown provider and trigger
runtime “Cannot find provider” failures.
Code

README.md[12]

Evidence
The README table shows github. while the runtime provider enum/typing and unit tests expect
github, proving the documentation is incorrect and would cause misconfiguration.

README.md[9-15]
src/runtime/models.ts[4-8]
src/schema-utils.ts[6-13]
test/token.test.ts[67-77]
test/unit/auth-provider-methods.test.ts[47-50]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The README provider table documents GitHub’s provider key as `github.` (trailing dot), but the actual provider key used throughout the codebase is `github`. This inconsistency will lead users to configure an invalid provider name and encounter runtime errors.

### Issue Context
The codebase defines supported providers as `local | github | google` and tests reference `github` as the provider key.

### Fix Focus Areas
- README.md[9-15]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

@dev-davexoyinbo dev-davexoyinbo merged commit aa33191 into main May 25, 2026
3 checks passed
Comment thread README.md
| -------- | -------- | ------ |
| Local | local | ✅ |
| GitHub | github | ✅ |
| GitHub | github. | ✅ |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Wrong github provider key 🐞 Bug ≡ Correctness

README.md lists the GitHub provider key as github. but the module’s supported provider identifier
is github, so users copying the documented key will configure an unknown provider and trigger
runtime “Cannot find provider” failures.
Agent Prompt
### Issue description
The README provider table documents GitHub’s provider key as `github.` (trailing dot), but the actual provider key used throughout the codebase is `github`. This inconsistency will lead users to configure an invalid provider name and encounter runtime errors.

### Issue Context
The codebase defines supported providers as `local | github | google` and tests reference `github` as the provider key.

### Fix Focus Areas
- README.md[9-15]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 2.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant