-
Notifications
You must be signed in to change notification settings - Fork 128
feat: add --reinstall-tui flag to force reinstall rogue-tui #78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ktej721
wants to merge
5
commits into
qualifire-dev:main
Choose a base branch
from
ktej721:feature/74-reinstall-tui
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3b811eb
feat: add --reinstall-tui flag to force reinstall rogue-tui
ktej721 643d6b6
docs: update docstring for install_rogue_tui
ktej721 f1f6f05
Merge branch 'main' into feature/74-reinstall-tui
ktej721 21ff3f0
Merge branch 'main' into feature/74-reinstall-tui
ktej721 cbecaf3
Merge branch 'main' into feature/74-reinstall-tui
yuval-qf File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
🧩 Analysis chain
Verify all call sites have been updated with the
forceparameter.The usage here is correct. However, based on the PR comments, there appears to be at least one more call to
install_rogue_tui()inrogue/common/update_checker.pythat may need updating to align with the new signature.Run the following script to find all call sites:
🏁 Script executed:
Length of output: 1353
Let me search for the
install_rogue_tuifunction definition to verify the expected parameters:The web search results are not relevant to the specific codebase. Let me search the codebase for the function definition directly:Length of output: 0
🏁 Script executed:
Length of output: 766
🏁 Script executed:
Length of output: 714
🏁 Script executed:
Length of output: 815
🏁 Script executed:
Length of output: 1213
🏁 Script executed:
Length of output: 95
Fix call to
install_rogue_tui()inrogue/common/update_checker.py—parameter name mismatch.The function signature expects a
forceparameter, but line 220 inrogue/common/update_checker.pypassesupgrade=Trueinstead. Update this call to useforce=True:🤖 Prompt for AI Agents