pipe-cd / pipe-cd/pipecd

Add a new field to show why command was failed.

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

Nobody has claimed this yet.

area/server good first issue kind/todo
Dominant language
Go
Stars
1.4k
Forks
364
Avg merge
1d 4h
Merged PRs (30d)
84

Description

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 with pkg/model/command.pb.go at lines 163-166 and review the TODO context introduced when PR #3342 was merged. Add a field that exposes why the command failed, then verify that the generated command model contains the failure reason.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.