Add rake task to release to rubygems and github

[ShockwaveNN]

I think it's never hurt to release this gem not only to rubygems.org, but also on GitHub packages

I'm not sure of exact of release process (didn't find any info), but I think rake task rake release is used.
If so - I created new task release_github_rubygems which first call rake release and after push resulting gem to Github packages.

Please not, that person, who perform releases should execute

echo ":github: Bearer GH_TOKEN" >> ~/.gem/credentials

before pushing gem. GH_TOKEN can be generated here

---

Before submitting the PR make sure the following are checked:

• Wrote good commit messages.
• Commit message starts with [Fix #issue-number] (if the related issue exists).
• 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.
• The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
• Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

[bbatsov]

I'd probably add a separate task to release to GitHub, plus some notes on using it, apart from the combined one. Then, again - I release using rake release, so I'm not sure I'll remember to run a new rake task going forward. :D

[ShockwaveNN]

I'd probably add a separate task to release to GitHub, plus some notes on using it, apart from the combined one.

Agree, will do

Then, again - I release using rake release, so I'm not sure I'll remember to run a new rake task going forward. :D

I think I can add releasing to github in default rake release task, but I don't think this is a good idea

[koic]

Is this a required release method for RuboCop only? Otherwise, for example, you can propose a command to RubyGems.

And users can confirm a released gem impact by numbers such as the number of downloads on rubygem.org. I'm curious about the advantages of adding publishing using a non-central hosted GitHub package :-)

[ShockwaveNN]

@koic Sorry, I'm not fully understand that you trying to say

I'm curious about the advantages of adding publishing using a non-central hosted GitHub package

I don't know about any REAL advantages, I was just interested to try it in my projects and I thought this may be good for my favorite open-source project, but if rubocop dev team see no advantage in this - I think we can just cancel that idea

[koic]

Thank you for replying. I'm also interested in the new GitHub Packages feature :-)

IMHO, For private internal hosting gems, using GitHub packages is convenient because hosting using gem server is not necessary. OTOH, for published available gems, it's better to release only to the centrally hosted rubygems.org. It would be simpler to focus on just one.

[ShockwaveNN]

It would be simpler to focus on just one.

So, to be clear - better close this PR?

[bbatsov]

Yeah, let's close it. Thanks for the suggestion, though!