Bad Migration Date checker checks non-ruby files when it shouldn't
Open
Nobody has claimed this yet.
bug
help wanted
pinned
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
Example from one of my PRs:
Some comments on commit https://github.com/Fryguy/manageiq/commit/d6ec1eeff40b6703205560431ee3144967836462
- :red_circle: Bad migration date: db/migrate/data/20160127210624_convert_configurations_to_settings_changes/broker_notify_properties.tmpl.yml
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 locating the bad migration date checker in the miq_bot repository and review the example commit d6ec1eeff40b6703205560431ee3144967836462. Reproduce or inspect why broker_notify_properties.tmpl.yml is reported, then verify that non-Ruby migration files are excluded from the checker’s results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100