-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactorcop refactors #2756
Refactorcop refactors #2756
Conversation
Should we add a |
@gogogarrett Yeah, potentially! Are you willing to handle that? It'd be great if we could see this sort of information when a pull request is opened, like a build fail/pass. |
I'm not a fan of this :( |
@simi it's not like we have to reject PRs outright, it's just nice to have the information. Refactor cop isn't intended to be followed 100%, it's just to promote discussion around code maintenance and technical debt introduction. |
@parndt actually I changed my mind. Are you still interested in merge? Rebase would be needed anyway. |
@simi rebased |
Sorry for obstructions @parndt. |
❤️💛💙💜💚💜💙💛❤️💛💙💜💚💜💙💛❤️❤️💛💙💜💚💜💙💛❤️💛💙💜💚💜💙💛❤️❤️💛💙💜💚💜💙💛❤️💛💙💜💚💜💙💛❤️❤️💛💙💜💚💜💙💛❤️💛💙💜💚💜💙💛❤️❤️💛💙💜💚💜💙💛❤️💛💙💜💚💜💙💛❤️❤️💛💙💜💚💜💙💛❤️💛💙💜💚💜💙💛❤️ |
This could be a work in progress, please contribute to this branch
refactorcop
if you want to address these issues one by one:http://www.refactorcop.com/refinery/refinerycms