4 ms·
This is great. But, I am sort of missing how this is any better than just having a PR and issue template on Github. Yes, it is automated and gives you neat bad
by madamelic 8y ago
This is great.
But, I am sort of missing how this is any better than just having a PR and issue template on Github. Yes, it is automated and gives you neat badges but I am not entirely sold on how much of an improvement this is for typical workflows.
- shinelay 8y agoWell PR and issue template doesn't ensure that you have consistency, people can erase the template and still leave the description blank. Mergeable ensures the consistency in the PR by making it un-mergeable until you follow the rule-set which is highly configurable.
- jusx 8y agoThere are few things that is useful: 1. I want to prevent accidental merges of work in progress or proof of concepts PRs. 2. I want to ensure that a PR has the right GH project associated with it because as part of our kanban process we have a stage for QA validation. If a PR or Issue is not on the board -- it won't get QA'd That's just some of the things. Also, there aren't any neat badges with mergeable... :-)