chore: introduce top-level Rakefile for easier task management across packages #120
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
jeeyyy
changed the title
jeeyyy
changed the title
scurker
reviewed
Jul 17, 2020
scurker
reviewed
Jul 17, 2020
|
Changes LGTM, just 2 questions. |
scurker
approved these changes
Jul 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In order to be able to execute the top level Rakefile tasks that are introduced.
Given the lerna-esque/ monorepo directory structure followed, the top level task is purely a bunch of helper to invoke either scoped or all rake tasks of individual tasks.
Rest of the work in this PR is cleanup.
Closes issue:
Reviewer checks
Required fields, to be filled out by PR reviewer(s)