wordpress-mobile / wordpress-mobile/release-toolkit
release-toolkit code refactoring (reorganize methods and files)
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 31
- Forks
- 10
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 2
Description
Refactor parts of the release-toolkit code in order to:
- Put some of the methods in better places – especially a lot of methods that are in
*_git_helperare not really related to git per se (and are probably only there because they end up pushing things at the of of what they actually do, which is only part of their action) - Make it more testable where needed
Note: We'll very likely work on the YARD doc issue #192 in parallel of working on this.
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 mapping the release-toolkit methods currently grouped in *_git_helper files and identifying which actions are not inherently Git-related. Review the existing structure and testing gaps before deciding how responsibilities should move. Done means the methods are organized by responsibility and the affected code is more testable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- release, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100