feat: allow local log entries to select an issue form
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli
Research direction
Start from the frog log command and the existing inbound.template resolution behavior. Trace how local forms are selected for scaffolding and body validation, then verify that --template accepts a path or filename, overrides the local form only when supplied, and preserves existing behavior when omitted.
Written by the indexing model from the issue text.
Description
Problem
A repository can currently configure one local issue form for every Frog entry. frog log --label can distinguish a class of friction, but the entry is still scaffolded and validated against the repository's single configured form.
Some friction needs structured evidence that does not fit the default form. For example, a flaky-test entry should capture the failing command and output, an unchanged passing retry, environment, and observed frequency.
Proposal
Add a local template override to frog log:
frog log --template flaky-test.yml --label flaky-test "test name: failure"
--template <path-or-name> would resolve the same way as inbound.template: either a full path or a filename under .github/ISSUE_TEMPLATE. When present, it would override the configured or discovered local form for scaffolding and body validation. Existing behavior would remain unchanged when omitted.
This keeps labels and issue forms composable without introducing a broader category or profile abstraction.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from wevm/frog
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
frog log rejects Windows repository rootsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
GitHub App token fallback misses recent issues in large repositoriesPossibly taken @blalor claimed this 59 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#280 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation story
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug category:billing priority:p3 track:fast
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LanternOps/breeze#9223 ·
Maintainers usually reply within 1 day