Skip to content

[task] Design safe workflow actions for future writes #25

Closed as not planned
Closed as not planned
[task] Design safe workflow actions for future writes#25
Labels
area: designUX, visual design, copy, screenshots, and design contribution workflow.kind: maintenanceRepository maintenance or infrastructure work.maintainer onlyRepository administration or governance work reserved for maintainers.status: staleAutomatically marked stale due to inactivity.
Milestone
v0.4.0 - Workflow Actions

Description

@phongndo
phongndo
opened on Apr 29, 2026

Goal

Design the safe write-action model for future workflow actions.

Why this matters

Nexgit should prove read-only GitHub workflow state before mutating GitHub. Once write actions are added, contributors and maintainers need explicit target confirmation and dry-run previews.

Command/API target

Produce a maintainer-owned design note for future actions such as issue claim/unclaim, review thread reply/resolve, and check rerun.

Depends on

  • v0.1 app-server data methods for the read-only state model.

Out of scope

  • Do not implement write actions in this issue.
  • Do not add OAuth or direct token management.
  • Do not design non-GitHub providers.

Definition of done

  • The design states which write actions are first.
  • The design requires explicit repository target display before mutation.
  • The design defines dry-run preview expectations.
  • The design lists permission and failure cases maintainers must review before implementation.

Verification

  • Design note or issue comment reviewed by a maintainer.
  • Any repo-doc change runs pnpm format:prettier:check.

Activity

  1. phongndo
    added this to the v0.4.0 - Workflow Actions milestone on Apr 29, 2026
  2. phongndo
    added
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    kind: maintenanceRepository maintenance or infrastructure work.
    maintainer onlyRepository administration or governance work reserved for maintainers.
    on Apr 29, 2026

  3. github-actions commented on Apr 29, 2026

    @github-actions
    github-actionsBot
    on Apr 29, 2026 – with GitHub Actions

    This issue needs a small update before triage:

    • Area must be one of Automation, CLI, Core, Desktop, Design, Docs, Protocol, Tests, or TUI so triage automation can route the issue.

    Please edit the issue instead of opening a new one.

  4. github-actions
    added
    needs: complianceThe author or reporter needs to fix template or policy gaps.
    and removed
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    on Apr 29, 2026
  5. phongndo
    added
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    and removed
    needs: complianceThe author or reporter needs to fix template or policy gaps.
    on Apr 29, 2026

  6. github-actions commented on Jun 1, 2026

    @github-actions
    github-actionsBot
    on Jun 1, 2026 – with GitHub Actions

    This issue has been quiet for a while. If it is still relevant, add context and it will stay open.

  7. github-actions
    added
    status: staleAutomatically marked stale due to inactivity.
    on Jun 1, 2026

  8. github-actions commented on Jun 15, 2026

    @github-actions
    github-actionsBot
    on Jun 15, 2026 – with GitHub Actions

    Closing due to prolonged inactivity. It can be reopened with fresh context.

  9. github-actions
    closed this as not plannedon Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: designUX, visual design, copy, screenshots, and design contribution workflow.kind: maintenanceRepository maintenance or infrastructure work.maintainer onlyRepository administration or governance work reserved for maintainers.status: staleAutomatically marked stale due to inactivity.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions