Noissue - Improve dependency management documentation

README.md

 Adblock Plus for Chrome, Opera, Microsoft Edge and Firefox
 ==========================================================
 
 This repository contains the platform-specific Adblock Plus source code for
 Chrome, Opera, Microsoft Edge and Firefox. It can be used to build
 Adblock Plus for these platforms, generic Adblock Plus code will be extracted
 from other repositories automatically (see _dependencies_ file).
 
 Note that the Firefox extension built from this repository is the new
 [WebExtension](https://developer.mozilla.org/en-US/Add-ons/WebExtensions).
@@ skipping 49 matching lines @@
 under _about:debugging_ in Firefox or in _Extensions_ menu in Microsoft Edge,
 after enabling extension development features in _about:flags_.
 After making changes to the source code re-run the command to update the
 development environment. In Chrome and Firefox the extension should reload
 automatically after a few seconds.
 
 Builds for Microsoft Edge do not automatically detect changes, so after
 rebuilding the extension you should manually force reloading it in Edge by
 hitting the _Reload Extension_ button.
 
+#### Skip dependencies check

[kzar, 2018/02/12 14:06:53]

Ditch the header IMO.

[a.giammarchi, 2018/02/12 15:02:23]

Done.

+
+If you are modifying `adblockpluscore` or `adblockplusui` and you would like

[kzar, 2018/02/12 14:06:53]

How about this?

The build script calls the ensure_dependencies script automatically to manage
the dependencies (see _dependencies_ file). Dependencies with local
modifications won't be updated. Otherwise during development specifying a
feature-branch's name for a dependency's revision is sometimes useful.
Alternatively dependency management can be disabled completely by setting the
_SKIP_DEPENDENCY_UPDATES_ environment variable, for example:

    SKIP_DEPENDENCY_UPDATES=1 ./build.py devenv -t chrome

[a.giammarchi, 2018/02/12 15:02:23]

Done.

+to build the dev extension, you can specify `SKIP_DEPENDENCY_UPDATES=true`
+as environment variable so that build tools will not ensure the release commit.
+
+    SKIP_DEPENDENCY_UPDATES=true ./build.py devenv -t chrome
+
 Running the unit tests
 ----------------------
 
 To verify your changes you can use the unit test suite located in the _qunit_
 directory of the repository. In order to run the unit tests go to the
 extension's Options page, open the JavaScript Console and type in:
 
     location.href = "qunit/index.html";
 
 The unit tests will run automatically once the page loads.
 
 Linting
 -------
 
 You can lint the code using [ESLint](http://eslint.org).
 
     eslint *.js lib/ qunit/ ext/ chrome/
 
 You will need to set up ESLint and our configuration first, see
 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-config-eyeo)
 for more information.