fly-apps / fly-apps/safe-ecto-migrations
For each section there should be a citation
Open
- Dominant language
- No language data
- Stars
- 387
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Some of the information is just stated without backing citations. This should be fixed. Each scenario should be verified, and when verified, a citation of the scenario, either pointing to official documentation or release notes, or a repeatable test scenario.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review each section and scenario in the safe Ecto migrations guide, then verify every claim against official documentation, release notes, or a repeatable test scenario. Done means each scenario has a supporting citation and the guide's statements are backed by evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100