Making this repo into a monorepo in preparation of more granular work (…

…microsoft#250)

* Turning lage into monorepo to prepare subdividing into pieces

* getting rid of renovate for now

* updated the root scripts to work

* fixing up pipelines

* moving many files around requires adjustments to beachball config

* upgrade node version to allow docusaurus to consume newer node version

* Change files

* get rid of the extra docs: prefix

* adding verbose logging

README.md

@@ -1,59 +1,7 @@
 # lage
 
-This is the UNSTABLE branch. All package published from this branch will be tagged as `lage@unstable`. When we have confirmed stability for v1.x branch, then we'll promote it to be stable.
-
 Documentation is here: https://microsoft.github.io/lage/
 
-## Overview
-
-Your JS repo has gotten large enough that you have turned to using a tool to help you manage multiple packages inside a repository. That's great! However, you realized quickly that the tasks defined inside the workspace have to be run in package dependency order.
-
-Lerna, Rush, wsrun and even pnpm will provide a simple way for you to run npm scripts to be run in a topological order. However, these tools will force you to run your tasks by script name one at a time. For example, all the `build` scripts will have to run first. Then all the `test` scripts run in the topological order.
-
-This usually means that there are wasted CPU cycles in between `build` and `test`. We can achieve better pipelining the npm scripts if we had a way to say that `test` can run as soon as `build` are done for the package.
-
-`lage` (Norwegian for "make", pronounced law-geh) solves this by providing a terse pipelining syntax. It has many features geared towards speeding up the task runner that we'll explore later.
-
-## Quick Start
-
-`lage` gives you this capability with very little configuration. First, let's install the `lage` utility. You can place this in your workspace's root `package.json` by running `yarn add`:
-
-```
-yarn add -D lage
-```
-
-Confirm with `yarn` that you are sure to add a package at the root level, you then place a root level script inside the `package.json` to run `lage`:
-
-```
-{
-  "scripts": {
-    "build": "lage build",
-    "test": "lage test"
-  }
-}
-```
-
-Add a configuration file in the root to get started. Create this file at the root `lage.config.js`:
-
-```js
-module.exports = {
-  pipeline: {
-    build: ["^build"],
-    test: ["build"],
-  },
-};
-```
-
-Do not worry about the syntax for now. We will go over the configuration file in a coming section. You can now run this command:
-
-```
-$ lage test
-```
-
-`lage` will detect that you need to run `build` steps before `test`s are run.
-
-
-
 # Contributing
 
 This project welcomes contributions and suggestions.  Most contributions require you to agree to a

beachball.config.js

@@ -8,9 +8,8 @@ module.exports = {
     'decks/**',
     'docs/**',
     'jasmine.json',
-    'jest.config.js',
-    'renovate.json',
-    'tests/**',
+    'packages/*/jest.config.js',
+    'packages/*/tests/**',
     // This one is especially important (otherwise dependabot would be blocked by change file requirements)
     'yarn.lock',
   ],

change/lage-1dd4d866-1d71-4df6-b911-a97902fdc51e.json

@@ -0,0 +1,7 @@
+{
+  "type": "patch",
+  "comment": "Moving to a monorepo. This will be a test publish",
+  "packageName": "lage",
+  "email": "ken@gizzar.com",
+  "dependentChangeType": "patch"
+}