ruby / ruby/rubygems

Print running shell commands when verbose is enabled

Open
#3,331 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bundler status: triage
Dominant language
Ruby
Stars
4k
Forks
1.9k
Avg merge
1d 2h
Merged PRs (30d)
81

Description

Hi,

I think --verbose should print out the executed command (I did it quite by mistake for git commands and it was quite informative) and also their outputs (that's how I saw the --no-hardlinks issue).

I'm sure there are other interesting areas to be verbose about but those were the pain points I had.

Thankfully ruby allows to edit gem's source code which is of great help but shouldn't be needed in most situations IMHO.

Thanks.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating how the --verbose option is handled and where shell commands such as git commands are executed. Compare the current behavior around the --no-hardlinks issue, then establish tests showing that verbose mode reports executed commands and their outputs.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.