NASA-IMPACT / NASA-IMPACT/veda-github-actions
[Backend]-[Objective 30]: Incident runbook automation
Open
Nobody has claimed this yet.
Objective
poc-loe
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 8
Description
Context
Motivation
Deliver Incident runbook automation to support the Disasters program during this PI.
Description
Scope, milestones, and dependencies for incident runbook automation.
Examples & Concept Diagrams (If applicable)
Success Criteria
- Design reviewed and approved
- Implementation merged and deployed
Risks
- Dependency slippage; mitigate with early integration checkpoints.
LOE/FTE
| Person | Role | FTE | Notes |
|---|---|---|---|
| Bob Martinez | Backend | 0.72 | — |
| Yuki Tanaka | ML | 0.72 | — |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the repository’s reusable GitHub Actions and the project-board scope for Objective 30; clarify the design, dependencies, deployment target, and approval criteria before implementation. Done means the design is approved and the implementation is merged and deployed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100