Skip to content

Conversation

@j-luong
Copy link
Contributor

@j-luong j-luong commented Jan 15, 2026

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Updates the list of CI env vars for isCI() checks.

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

Risk assessment (Low | Medium | High)?

Low - additive changes to isCI()

@j-luong j-luong requested review from a team as code owners January 15, 2026 12:24
@github-actions
Copy link
Contributor

github-actions bot commented Jan 15, 2026

Warnings
⚠️

You've modified files in src/ directory, but haven't updated anything in test folder. Is there something that could be tested?

Generated by 🚫 dangerJS against 0fda9ea

@j-luong j-luong force-pushed the chore/cli-1231_updateIsCIChecks branch from d3e2892 to 0fda9ea Compare January 19, 2026 16:44
@j-luong j-luong enabled auto-merge January 19, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants