mudler/luet

Verbose reclaim output

Open

#107 opened on May 6, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (29 forks)github user discovery
good first issue

Repository metrics

Stars
 (304 stars)
PR merge metrics
 (Avg merge 1h 36m) (16 merged PRs in 30d)

Description

reclaim should be more verbose on what it's doing

Contributor guide

Research direction
Locate the reclaim command implementation in the codebase and identify where progress messages can be added. Study existing logging patterns using the project's logger.
Tech stack
go
Domain
backendcli
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
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80