Add option to automatically update requirements.txt file

[danifr]

No description provided.

[simion]

AI review - Claude

🟡 Suggestion (3)

• Silent override of explicit -p when combined with --update-requirements — pip_upgrader/cli.py (line 76)
  If a user passes both --update-requirements and -p django, their explicit package selection is silently replaced with ['all']. This is surprising behavior — the user likely expects either an error or for both flags to coexist sensibly.
• Flag name is misleading — the tool always updates requirements — pip_upgrader/cli.py (line 5)
  The name --update-requirements implies the tool doesn't normally update requirements files, but it always does. The flag actually means 'select all packages without prompting.' A name like --all or --non-interactive would better communicate its behavior. Additionally, this is functionally identical to the existing -p all, so consider whether a new flag is warranted at all.
• No test coverage for the new flag — pip_upgrader/cli.py (line 75)
  The new --update-requirements flag has no tests. At minimum, a test should verify that passing this flag results in all upgradable packages being selected (equivalent to -p all).

Bottom line: The implementation is correct but the flag name is misleading (the tool always updates requirements — this flag just skips the prompt), it silently overrides -p, and it ships without tests. Consider renaming to --all or --non-interactive, handling the -p conflict explicitly, and adding test coverage.

Automated review by reviewd in 54s. Findings are AI-generated and may not be accurate.
Replies to this comment are not monitored.

[danifr]

I think I addressed all the comments
Let me know if you want me to squash the commits in one and if you want a particular commit message. Thanks!

[simion]

awesome, thanks for the contruibution! merged, releasing now.