sassoftware / sassoftware/arke
Automate module and submodule tagging via commit
Open
Nobody has claimed this yet.
automation
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 8
Description
Create a workflow that uses sassoftware/gotagger to tag arke, arke/api or arke/tests/integration. Only tag the modules referenced in the commit message (like how we do internally).
See their action for how they use it for their repo.
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
Start by reading the linked sassoftware/gotagger action workflow and inspect the repository's existing GitHub workflows. Determine how commit messages identify arke, arke/api, or arke/tests/integration. Done means commits tag only the modules named in their messages, matching the referenced internal behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100