Add Revise to the workflow section (JuliaLang#31580)

https://discourse.julialang.org/t/is-it-possible-to-integrate-revise-jl-into-the-base-library-of-julia/22291/10

doc/src/manual/workflow-tips.md

@@ -66,3 +66,69 @@ line. A common pattern includes the following elements:
 
 It is also possible to interact with a Julia REPL in the browser via [IJulia](https://github.com/JuliaLang/IJulia.jl).
 See the package home for details.
+
+## Revise-based workflows
+
+Whether you're at the REPL or in IJulia, you can typically improve
+your development experience with
+[Revise](https://github.com/timholy/Revise.jl).
+It is common to configure Revise to start whenever julia is started,
+as per the instructions in the [Revise documentation](https://timholy.github.io/Revise.jl/stable/).
+Once configured, Revise will track changes to files in any loaded modules,
+and to any files loaded in to the REPL with `includet` (but not with plain `include`);
+you can then edit the files and the changes take effect without restarting your julia session.
+A standard workflow is similar to the REPL-based workflow above, with
+the following modifications:
+
+1. Put your code in a module somewhere on your load path. There are
+ several options for achieving this, of which two recommended choices are:
+
+ a. For long-term projects, use
+ [PkgTemplates](https://github.com/invenia/PkgTemplates.jl):
+
+ ```julia
+ using PkgTemplates
+ t = Template()
+ generate("MyPkg", t)
+ ```
+ This will create a blank package, `"MyPkg"`, in your `.julia/dev` directory.
+ Note that PkgTemplates allows you to control many different options
+ through its `Template` constructor.
+
+ In step 2 below, edit `MyPkg/src/MyPkg.jl` to change the source code, and
+ `MyPkg/test/runtests.jl` for the tests.
+
+ b. For "throw-away" projects, you can avoid any need for cleanup
+ by doing your work in your temporary directory (e.g., `/tmp`).
+
+ Navigate to your temporary directory and launch Julia, then do the following:
+
+ ```julia
+ pkg> generate MyPkg # type ] to enter pkg mode
+ julia> push!(LOAD_PATH, pwd()) # hit backspace to exit pkg mode
+ ```
+ If you restart your Julia session you'll have to re-issue that command
+ modifying `LOAD_PATH`.
+
+ In step 2 below, edit `MyPkg/src/MyPkg.jl` to change the source code, and create any
+ test file of your choosing.
+
+2. Develop your package
+
+ *Before* loading any code, make sure you're running Revise: say
+ `using Revise` or follow its documentation on configuring it to run
+ automatically.
+
+ Then navigate to the directory containing your test file (here
+ assumed to be `"runtests.jl"`) and do the following:
+
+ ```julia
+ julia> using MyPkg
+
+ julia> include("runtests.jl")
+ ```
+
+ You can iteratively modify the code in MyPkg in your editor and re-run the
+ tests with `include("runtests.jl")`. You generally should not need to restart
+ your Julia session to see the changes take effect (subject to a few limitations,
+ see https://timholy.github.io/Revise.jl/stable/limitations/).