Conversation
… from the copilot package root instead of the current working directory. Update type definitions and add documentation for clarity on path resolution in different contexts.
…ACCESS_TOKEN availability. Introduce functions to check token presence in environment and .env file, ensuring setup continuity. Update copySetupFiles to handle token checks and improve logging for user guidance on token setup.
…sence in parameters and adding comments for clarity on token validation coverage in related tests.
…commands, including handling non-GitHub URLs, errors in `getGitInfo`, and missing issue numbers. Introduce emoji-based title formatting in `IssueRepository` based on labels, ensuring proper representation for different issue types. Improve test coverage for issue state transitions and context fallbacks.
…nd update related use cases to utilize it. Enhance tests for publicUrl functionality to ensure correct URL generation based on project details.
…nd update related use cases to utilize it. Enhance tests to verify correct URL generation when project URL is absent.
|
To view this pull requests documentation preview, visit the following URL: Documentation is deployed and generated using docs.page. |
vypbot
added
the
size: XXL
Closed
1 task
vypbot
reviewed
Feb 14, 2026
vypbot
reviewed
Feb 14, 2026
vypbot
reviewed
Feb 14, 2026
vypbot
reviewed
Feb 14, 2026
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…rovision via command line, improving user guidance on token requirements. Update tests to verify behavior when token is provided, ensuring proper handling of setup conditions.
…mand line input, enhancing user guidance on token requirements. Update tests to ensure correct behavior for token validation and fallback mechanisms.
…itize command line input and improve validation logic. Enhance error logging for project item retrieval and update tests to cover pagination scenarios and invalid project IDs.
…r command line token input, ensuring correct token handling in parameters. Update test to reflect the expected token value for improved clarity and validation.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #310 +/- ##
===========================================
+ Coverage 88.82% 90.23% +1.41%
===========================================
Files 134 134
Lines 5941 6014 +73
Branches 1272 1293 +21
===========================================
+ Hits 5277 5427 +150
+ Misses 250 194 -56
+ Partials 414 393 -21
🚀 New features to boost your workflow:
|
…exit when no valid PERSONAL_ACCESS_TOKEN is provided. Update tests to verify correct logging and exit behavior based on the presence of a .env file, enhancing user guidance during setup.
vypbot
reviewed
Feb 15, 2026
| logInfo(' • Or create a .env file in this repo with: PERSONAL_ACCESS_TOKEN=your_github_token'); | ||
| } | ||
| process.exit(1); | ||
| return; |
Contributor
There was a problem hiding this comment.
Unreachable code after process.exit(1)
Severity: low
Location: src/cli.ts:459
Line 459 contains a return; statement immediately after process.exit(1) on line 458. Since process.exit() terminates the process immediately, the return statement is unreachable and should be removed as it's dead code.
Suggested fix:
Remove the unreachable return; statement on line 459 since process.exit(1) on line 458 already terminates execution.
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
This was referenced Feb 15, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on my analysis of the issue and codebase, I can see the problem. When running
copilot setupon a project that doesn't have anaction.ymlfile (like thezstandardproject mentioned), theloadActionYaml()function insrc/utils/yml_utils.tscrashes because it tries to read the file without checking if it exists first.📌 Summary
Fixes a crash that occurs when running
copilot setupon a repository that doesn't contain anaction.ymlfile. The setup command now gracefully handles missing action configuration files instead of throwing an ENOENT error.🎯 Related Issues / Tickets
🧩 Scope of Changes
loadActionYaml()function to gracefully handle missingaction.ymlfilesgetActionInputs()andgetActionInputsWithDefaults()to return empty objects when action.yml is not found🛠️ Technical Details
The
loadActionYaml()function insrc/utils/yml_utils.tswas attempting to readaction.ymlfrom the package root without first verifying the file exists. When runningcopilot setupon a repository that doesn't have copilot installed (like thezstandardproject mentioned in the issue), this caused a fatal ENOENT crash.The fix adds proper file existence checking using
fs.existsSync()before attempting to read the file. Ifaction.ymlis not found, the function now returns a default empty configuration object instead of throwing an error. This allows the setup process to continue and copy the necessary template files to the target repository.🔍 How to Test
zstandard)copilot setupfrom within that repository.github/workflows/,.github/ISSUE_TEMPLATE/, and.github/pull_request_template.mdare created🧪 Test Coverage
Manual testing is appropriate here as the fix involves file system interactions that are best verified through integration testing.
🚀 Deployment Notes
🔒 Security Considerations
📈 Performance Impact
📝 Notes for Reviewers
The fix ensures backward compatibility while preventing crashes on fresh repositories. The empty object fallback maintains existing behavior for repositories that do have
action.ymlconfigured.✅ Checklist
📚 Additional Context
This fix addresses the issue where running
copilot setupon external repositories (repositories that don't have copilot's GitHub Action configured) would crash with:The error occurred because the CLI was trying to load action inputs from a file that doesn't exist in the target repository.