Skip to content

Did this repository work move somewhere else? #378

Open

Description

@lkraav

Hi. I took a break from gh-aw and resumed today to update workflows. Now last commit here is from 1mo ago 42c2ab5

Is this repo on its way to archived, and what's the current authoritative workflow source code.. souce then?

cc @dsyme maybe?

Activity

  1. dsyme commented on Aug 24, 2026

    @dsyme
    Contributor

    Hi @lkraav

    This repo is still active, though we are definitely thinking about how to build a set of top-priority workflows and to make installation easier.

    We also welcome contributions here, and updates.

    Many thanks

  2. lkraav commented on Aug 24, 2026

    @lkraav
    Author

    This repo is still active, though we are definitely thinking about how to build a set of top-priority workflows and to make installation easier.

    We also welcome contributions here, and updates.

    Thanks. I'll continue to gh aw update from here and see if there's anything we can come up with to help.

    In connection to this, I started thinking "After a break, how do I even recall where my agentic workflows are sourced from", and gh aw list doesn't really help... wondering now if -v could build a source column, or am I just missing some existing way?

    main(+80/-12,10)+ ± gh aw list -v
    Listing workflow files
    Found 5 markdown workflow files
    ✓ Found 5 workflows
    ╭─────────────────────────┬─────────┬──────────╮
    │ workflow                │ engine  │ compiled │
    ├─────────────────────────┼─────────┼──────────┤
    │ code-simplifier         │ copilot │ No       │
    │ daily-file-diet         │ copilot │ Yes      │
    │ daily-test-improver     │ copilot │ Yes      │
    │ daily-typescripter      │ copilot │ Yes      │
    │ duplicate-code-detector │ copilot │ Yes      │
    ╰─────────────────────────┴─────────┴──────────╯
    
  3. dsyme commented on Aug 24, 2026

    @dsyme
    Contributor

    @lkraav Adding a source colum to gh aw list by default makes total sense. If you added the workflows via gh aw add or gh aw add-wizard the source information should be in the installed workflow, so it should be possible to do no problem.

    Could you add an issue to gituhb/gh-aw about this along with any other usability/quality-of-life improvements you notice please, we're happy to action user feedback like this quickly :)

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions