pipe-cd/pipecd

Add a new field to show why command was failed.

Open

#3,344 opened on Mar 4, 2022

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Go (319 forks)auto 404
area/servergood first issuekind/todo

Repository metrics

Stars
 (1,329 stars)
PR merge metrics
 (PR metrics pending)

Description

Contributor guide

Research direction
Examine the command model in pkg/model/command.pb.go and add a new field for failure reason, then update related logic.
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.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Goprotobuf
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65