Show custom cops in --show-cops

[ptarjan]

Before submitting a PR make sure the following are checked:

• Wrote good commit messages.
• Used the same coding conventions as the rest of the project.
• Feature branch is up-to-date with master (if not - rebase it)
• Squashed related commits together.
• Added tests.
• Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
• All tests are passing.
• The new code doesn't generate RuboCop offenses.
• The PR relates to only one subject with a clear title
  and description in grammatically correct, complete sentences.

[Neodelf]

Damn it! Pull request which resolves the issue was already created. May be I was should make a mark about it?

[bbatsov]

I don't have a preference who's PR we'll merge eventually. It's simply important to fix the issue at hand.

[ptarjan]

ditto

[Neodelf]

I just wanted to draw attention. I apologize if my words seem rude. Only positive! :)

[bbatsov]

@ptarjan Please, rebase this.

[ptarjan]

I'd love to figure out a way to do CHANGELOGs without getting so many merge conflicts.

[bbatsov]

I'd love to figure out a way to do CHANGELOGs without getting so many merge conflicts.

Who wouldn't. :-) Unfortunately all automated solutions produce crappy changelogs and I don't want to write one just before the release.

The build is broken, btw.

[bbatsov]

P.S. I plan to cut a new release soon.

[ptarjan]

@bbatsov excited for the new cut. I rebased and repushed. That CHANGELOG will be the death of me.

[bbatsov]

That CHANGELOG will be the death of me.

I don't like dealing with it either, but it's pretty useful at release time. :-)

[ptarjan]

Agreed, I just wish there was a format which didn't always merge conflict.