livebud/bud

Improve bud create logging

Open

#362 opened on Jan 20, 2023

View on GitHub
 (2 comments) (2 reactions) (0 assignees)JavaScript (211 forks)batch import
help wantedimprovement

Repository metrics

Stars
 (5,391 stars)
PR merge metrics
 (PR metrics pending)

Description

$ bud create testbud
| Created: go.mod
| Created: package.json
| Created: .gitignore
| Created: public/favicon.ico
| Installed: go modules
| Installed: node modules
| Generated: bud
| Ready: testbud
  1. I think we should say Created: testbud/go.mod, etc. because it was unclear where those files were being written.
  2. We should be more explicit about next steps, maybe cd testbud && bud run?

Any sources of inspiration we could draw on here from other libraries and ecosystems?

Contributor guide

Research direction
Examine the `create` command source code and modify the logging statements to include the full path and next steps.
Tech stack
go
Domain
clideveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85