Command-line option "--bare" has no effect in "sync" and "clean" actions
See original GitHub issueIssue description
The --bare
flag is supposed to set “minimal output” in sync
and clean
, but I don’t see any difference with and without it. Looking at the code implementing those actions, I see bare
in the list of parameters for do_sync
and do_clean
, but they are not used anywhere in the body of those functions.
Expected result
No output when --bare
is used in pipenv sync
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Command-Line Reference | Bazel
This flag has no effect on all other platforms but is supported to ensure rc files can be shared among them without changes....
Read more >p4 clean - Helix Core Command-Line (P4) Reference (2022.2)
The p4 clean command is equivalent to the p4 reconcile -w command. ... To preview the set of proposed workspace reconciliation actions, use...
Read more >Unison User Manual - UPenn CIS
Unison is a file-synchronization tool for Unix and Windows. It allows two replicas of a collection of files and directories to be stored...
Read more >Command Line Interface Guidelines
An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
Read more >hg - Mercurial SCM
The hg command provides a command line interface to the Mercurial system. ... Deleting or moving a bookmark has no effect on the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was closed in #3126 by way of #3064 and will be in the next release, thanks @jcrotts!
Opened a PR for this, I think it addresses the behavior you described @cubranic .