v15 - Dev workflows and tools
Open
Nobody has claimed this yet.
v15
- Dominant language
- Python
- Stars
- 279
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Description
Determine which CI/CD, linters and Dev tools to use and standardise the config
Improve dev experience and standardise code formatting, etc.
- scope which tools, actions etc. we want to use
- standardise where config files live, .github, top level or config
- decide on flake8/ruff rule set
- flake8 config file
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
Review the existing CI/CD, linter, and developer-tool configuration, including possible locations in .github, the repository top level, and a config directory. Identify the tools and actions to standardise, decide the flake8/ruff rule set, and define the final configuration locations; done means these choices and the resulting configuration are documented and consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100