thoughtbot / thoughtbot/factory_bot
Meta Issue on Issues
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 8.2k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Those maintainers 🤣 (I'm calling myself out in good fun)…
…should clean up old issues and resolve, close, or otherwise address them. Some seem to be open potentially as a reminder to document the solution or workaround. Others may no longer be relevant.
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 reviewing the repository's older open issues and identify which remain relevant. For each candidate, determine whether it should be resolved, closed, otherwise addressed, or documented with its solution or workaround; the work is done when the applicable old issues have been handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100