Skip to content

What is the best workflow after ce:review - worth introducing a ce:fix? #562

@naz

Description

@naz

Why?

There's uncertainty currently on what to do when issues come up during the ce:review.

Context

I find myself wondering what's the best flow to run after ce:review finishes with a whole bunch of P1s and P2s. Usually end up with ce:work pointing it to the findings above or plan fix all of the P1 ... . The ce:review seems to need something extra to close the loop (or maybe just better documentation?)

The way I'd see the flow working:

ce:work → ce:review → (if issues) ce:fix → ce:review (repeat until no issues) → ce:compound

Curious about the internal flow at Every for this part and what others have experimented with 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions