Skip to content

LAUNCH.md

Latest commit

 

History

History
76 lines (48 loc) · 2.31 KB

LAUNCH.md

File metadata and controls

76 lines (48 loc) · 2.31 KB
Raw

Launch kit — gitwork v0.1

One-liner

gitwork turns GitHub into your work OS: OOO coverage, a forward-looking daily desk, and issue-dependency critical path — CLI + Actions, no SaaS.

Show HN

Title: Show HN: gitwork – OOO coverage, daily work desk, and issue critical path on GitHub

Body:

I got tired of GitHub being “where code lives” while standups, coverage handoffs,
and dependency planning lived everywhere else.

gitwork is a small CLI (+ Actions) with three commands:

1. gitwork ooo — set status, reassign open review requests, comment on assigned
   work, open a coverage issue; reverse it with ooo end
2. gitwork today — what needs YOU today (reviews, CI red, ready-to-merge,
   unblocked assigned issues, SLA breaches) — not “what did I do yesterday”
3. gitwork path — waves + unlock bottlenecks from native blocked-by (with
   markdown Depends on: fallback)

No AI required. MIT. Node 20.

npm i -g github:Sqlace/gitwork#v0.1.0
# or after npm publish: npm i -g gitwork-cli
gh auth login
gitwork today

Repo: https://github.com/Sqlace/gitwork

Reddit — r/SideProject

Title: gitwork – make GitHub your actual work OS (OOO + daily desk + dependency path)

Body:

Built this after seeing the same complaints across r/github / devops / ExperiencedDevs:

- Reviews pile up while you’re on PTO (status alone doesn’t help)
- Standup tools look backward; mornings need a forward action queue
- Native issue dependencies shipped, but critical-path reporting is still thin

gitwork = CLI + GitHub Actions, AI optional (default = none).

Commands: ooo | today | path

Feedback welcome — especially on the OOO reassignment edge cases.

Reddit — r/github

Title: CLI/Action: Out-of-office coverage + personal work desk + blocked-by critical path

Body: short version of the SideProject post + install snippet.

Reddit — r/devops

Title: Drop-in GitHub Action for weekly issue dependency critical path reports

Focus on gitwork path --post cron and Mermaid output for standup screens.

Checklist before posting

  • Public repo
  • Release v0.1.0 tag
  • README install path uses real username
  • npm test green on CI
  • 15s demo GIF or asciinema of ooo start --dry-run + today + path
  • Replace Sqlace placeholders in README / LAUNCH