This repository has been archived by the owner on Mar 5, 2018. It is now read-only.
Organise by package manager, not language #55
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
greysteil
force-pushed
the
organise-by-package-manager
branch
from
d1bd569
to
7a9459e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some languages (cough JavaScript cough) have more than one package manager in active use. That makes our current structure, which is by language, look a little unhelpful.
This renames
languagethepackage_managereverywhere, removeslanguagefromBump::Repoentirely (it was unused) and renames all our classes from e.g.,UpdateCheckers::RubytoUpdateCheckers::Ruby::Bundler.In doing so, it lays the groundwork for supporting npm5.
If it's not immediately obvious, all of the above is massively breaking.