Bug 1460067 - Update references to devtools-core in devtools documentation;r=jlast
authorJulian Descottes <jdescottes@mozilla.com>
Wed, 09 May 2018 00:07:58 +0200
changeset 417550 dbece7696f795364bd52e1d579db47a7692fcf32
parent 417549 4614964298a87a20ad4cad2c721d25889b949b18
child 417551 1aeaff1e13f80f4ca820497345b279e67667f23b
push id33970
push usercsabou@mozilla.com
push dateWed, 09 May 2018 17:26:50 +0000
treeherdermozilla-central@d4d7e793ebe8 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersjlast
bugs1460067
milestone62.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1460067 - Update references to devtools-core in devtools documentation;r=jlast MozReview-Commit-ID: FWqWe0xoBrR
devtools/client/netmonitor/README.md
devtools/client/shared/components/reps/README
devtools/client/shared/source-map/README
devtools/client/webconsole/README.md
--- a/devtools/client/netmonitor/README.md
+++ b/devtools/client/netmonitor/README.md
@@ -66,17 +66,17 @@ Open `localhost:8000` in any browser to 
 ### Develop with related modules
 
 When working on make the Network Monitor running in the browser tab, you may need to work on external modules. Besides the third party modules, here are modules required for the Network Monitor and is hosted under `devtools-html` (modules shared across Devtools):
 
 * [devtools-config](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-config/#readme) config used in dev server
 * [devtools-launchpad](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-launchpad/#readme) provide the dev server, landing page and the bootstrap functions to run devtools in the browser tab.
 * [devtools-modules](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-modules/#readme) Devtools shared and shim modules.
 * [devtools-source-editor](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-source-editor/#readme) Source Editor component.
-* [devtools-reps](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-reps/#readme) remote object formatter for variables representation.
+* [devtools-reps](https://github.com/devtools-html/debugger.html/blob/master/packages/devtools-reps/#readme) remote object formatter for variables representation.
 
 Do `yarn link` modules in related module directory, then do `yarn link [module-name]` after `yarn install` modules.
 
 ## Code Structure
 
 Top level files are used to launch the Network Monitor inside of the DevTools toolbox or run in the browser tab (experimental). The Network Monitor source is mainly located in the `src/` folder, the same code base is used to run in both environments.
 
 We prefer use web standard API instead of FIrefox specific API, to make the Network Monitor can be opened in any browser tab.
--- a/devtools/client/shared/components/reps/README
+++ b/devtools/client/shared/components/reps/README
@@ -1,7 +1,7 @@
-Reps are now maintained on GitHub at: https://github.com/devtools-html/devtools-core/tree/master/packages/devtools-reps
+Reps are now maintained on GitHub at: https://github.com/devtools-html/debugger.html/tree/master/packages/devtools-reps
 
-All the files in this folder are copied from the devtools-core github repository and
+All the files in this folder are copied from the debugger.html github repository and
 should not be modified here.
 
 For any issue or feature request on Reps, please log an issue at
-https://github.com/devtools-html/devtools-core/issues with the label "Reps".
+https://github.com/devtools-html/debugger.html/issues with the label "devtools-reps".
--- a/devtools/client/shared/source-map/README
+++ b/devtools/client/shared/source-map/README
@@ -1,12 +1,12 @@
 devtools-source-map is maintained on GitHub at:
 
-https://github.com/devtools-html/devtools-core/tree/master/packages/devtools-source-map
+https://github.com/devtools-html/debugger.html/tree/master/packages/devtools-source-map
 
 All the files in this folder are copied from the above repository and
 should not be modified here.
 
 For any issue or feature request on devtools-source-map, please log an issue at:
 
-https://github.com/devtools-html/devtools-core/issues
+https://github.com/devtools-html/debugger.html/issues
 
-and label it with "source-map".
\ No newline at end of file
+and label it with "devtools-source-map".
\ No newline at end of file
--- a/devtools/client/webconsole/README.md
+++ b/devtools/client/webconsole/README.md
@@ -68,17 +68,17 @@ the WebConsole runs in a browser tab.
 When working on console running via launchpad, you may need to modify code on external modules.
 Besides the third party modules, here are modules required for the WebConsole
 (hosted under the `devtools-core` Github repo, which contains modules shared across Devtools).
 
 * [devtools-config](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-config/#readme) config used in dev server
 * [devtools-launchpad](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-launchpad/#readme) provide the dev server, landing page and the bootstrap functions to run devtools in the browser tab.
 * [devtools-modules](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-modules/#readme) Devtools shared and shim modules.
 * [devtools-source-editor](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-source-editor/#readme) Source Editor component.
-* [devtools-reps](https://github.com/devtools-html/devtools-core/blob/master/packages/devtools-reps/#readme) remote object formatter for variables representation.
+* [devtools-reps](https://github.com/devtools-html/debugger.html/blob/master/packages/devtools-reps/#readme) remote object formatter for variables representation.
 
 Changes to those modules need to be done on Github, using the Pull Request workflow.
 Then, a new version of the modified package need to be released on npm so the version number
 can be updated in WebConsole's `package.json`. Some modules have a release process,
 look for `RELEASE.md` file in the module folder, or ask a maintainer if you are
 unsure about the release process.
 
 ## Code Structure