kworkflow / kworkflow/kworkflow
Migrate to sourcehut
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Shell
- Stars
- 191
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Description
Description:
It is time to move to Sourcehut for consistency's sake. We need:
- Figure out how to migrate the workflow integration.
- How to migrate issues.
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
The issue names no files, tests, or entry points. Start by identifying how the workflow integration and issue tracking are currently hosted, then define the migration scope for both parts. Done means the workflow integration and issues have been migrated to Sourcehut and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100