Further GithubService cleanup
Open
Nobody has claimed this yet.
help wanted
pinned
refactoring
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
(From Gitter convo with @Fryguy)
Now that github_service is complete...can you move GithubUsageTracker underneath it? Thinking something like GithubService::UsageTracker
Also thinking OffenseMessage should move under MessageBuilder (maybe)
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
Search the repository for GithubUsageTracker, GithubService, OffenseMessage, and MessageBuilder, then inspect their references and any related tests. Done means the requested class organization is agreed and implemented without breaking existing references or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100