Conversation
- Fix extra closing brace in parseRepoUrl template literal
- Fix duplicate 'the' in error message ('the the branch' -> 'the branch')
There was a problem hiding this comment.
Pull request overview
This PR updates user-facing error strings in the GitHub analysis feature to correct minor typos and improve message clarity.
Changes:
- Fix an extra
}character in the “Error parsing repo url …” message. - Remove a duplicated word in the “Can’t access the … branch …” error message.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| `Can't access the the branch ${chalk.bold(reference)} on ${chalk.bold( | ||
| `Can't access the branch ${chalk.bold(reference)} on ${chalk.bold( | ||
| repoUrl | ||
| )} make sure it exits.` |
There was a problem hiding this comment.
The error message still has a typo: "make sure it exits" reads like "exit" rather than "exist". Update it to "make sure it exists" so the guidance is clear to users.
| )} make sure it exits.` | |
| )} make sure it exists.` |
| const [owner, repo] = slug.split('/') | ||
| if (!owner || !repo) { | ||
| throw new Error(`Error parsing repo url ${repoUrl}}`) | ||
| throw new Error(`Error parsing repo url ${repoUrl}`) |
There was a problem hiding this comment.
PR description says the original string "${repoUrl}}" would have caused a JavaScript syntax error, but that extra } was just a literal character after the interpolation and would still parse. Consider adjusting the PR description to reflect that this was a typo in the message, not a runtime syntax error.
Fixed two typos in the codebase:
${repoUrl}}→${repoUrl}- This would have caused a JavaScript syntax error at runtimeCan't access the the branch→Can't access the branchThese are minimal but concrete fixes that improve code quality.