Uh oh!
There was an error while loading. Please reload this page.
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.
CopilotAIMar 9, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The codebase has an established
getBooleanInput()utility insrc/util.tsthat handles case-insensitive comparison (via.toUpperCase() === 'TRUE'). It's used for all other boolean inputs:check-latestinsetup-java.ts:30,overwrite-settingsinauth.ts:20andtoolchains.ts:30.Using raw string comparison
=== 'false'here is fragile — it won't match'False'or'FALSE', which users might reasonably pass. This should usegetBooleanInputfromsrc/util.tsinstead, with the logic inverted (skip save when the result isfalse).Additionally, the input name
'cache-write'is hardcoded as a string literal, whereas the codebase convention is to define input name constants insrc/constants.ts(e.g.,INPUT_CACHE,INPUT_CACHE_DEPENDENCY_PATHat line 20-21). A constant likeINPUT_CACHE_WRITEshould be added there and used here.