Skip to content

feat: gc should configure beads to suppress this error message: "Creating issue without description." #54

@csells

Description

@csells

Before you continue

  • I searched existing issues and did not find a duplicate.
  • I can explain the user problem this solves, not just the implementation I prefer.

Problem to solve

Creating a bead with a freshly installed gc yields this:

⚠ Creating issue without description.
  Issues without descriptions lack context for future work.
  Consider adding --description="Why this issue exists and what needs to be done"

Agents can certainly execute beads w/o this, so the error seems unnecessary.

Proposed change

I'd like gc to configure beads to suppress this error message.

Alternatives considered

No response

Scope and impact

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/choreInternal improvement (refactor, tests, CI, tooling)priority/p3Backlog — good idea, reviewed when there's bandwidth

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions