Implement an init subcommand that scaffolds different workflows
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 2
- Forks
- 0
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 49
Description
Add an init subcommand that scaffolds different workflows.
- GHA workflow into a repository to publish markdown files (
markfluence update)- Scope / open questions:
- Exactly which workflow to write (trigger, steps, how
markfluenceis installed, how creds are provided via secrets). - Idempotency / not clobbering an existing workflow.
- Exactly which workflow to write (trigger, steps, how
- Scope / open questions:
.envfile for workflow where the user is editing docs in a directory they push to Confluence by handmarkfluence.yamlfile to denote project root- maybe Claude bits to make markfluence parts of the project clearer
Contributor guide
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 implementation files, tests, or entry points are named. First clarify which init artifacts are in scope, the workflow's triggers, installation and credential handling, and how existing files remain safe. Done should mean the agreed artifacts are generated idempotently with documented behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100