When running chef generate w/o git being setup everything blows up
Open
Nobody has claimed this yet.
Triage: Confirmed
Type: Bug
- Dominant language
- Ruby
- Stars
- 18
- Forks
- 23
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
This is a very unpleasant experience that we need to figure out how to fix. We should probably do a check to make sure git is configured either in the chef run and give a nice output or we should check before we run chef in the command.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with chef generate when git is not configured, then trace the command entry point to determine where the error occurs. The issue proposes either checking git during the run or before invoking the command; done means a clear, graceful diagnostic instead of the current failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100