fix: allow dot-sourced install in CI with opt-out - #138
Conversation
|
Warning Review limit reachedNext included review available in 16 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughThe installer adds ChangesInstall gating
Merge Risk: 🟠 High · up to The CI workflow runs repository code while checkout credentials remain available and grants a broader token than necessary, which could expose credentials or enable unintended repository actions if the executed code is compromised. Merge should wait for workflow hardening or explicit security acceptance. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 11922b19-302f-4460-a9d2-2c80554944d9
📒 Files selected for processing (2)
install.ps1test/install.Tests.ps1
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
7f55145 to
183da97
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 43b54f19-8a10-4c20-bc28-e056f34f392d
📒 Files selected for processing (1)
install.ps1
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: e7b8b763-0cb1-4364-a368-5dc59b994d4b
📒 Files selected for processing (1)
.github/workflows/ci.yml
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
fix regression in #136
The initial goal of #136 was to decouple function imports from the install flow so that installing Scoop wouldn't be triggered in our tests. However, I overlooked the fact that CI environments (such as GitHub Actions) execute script blocks within job steps using dot-sourcing; consequently, the changes in #136 broke the standard
run: irm get.scoop.sh | iexusage.This PR restores the original behavior while still preventing Scoop installation during tests, by allowing triggering the install flow when the
$env:CIvariable is present, while also providing aSCOOP_NOINSTALLenvironment variable to opt out of the install flow.