[pull] master from plotly:master

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: plotly
+custom: https://plot.ly/products/consulting-and-oem/

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,7 @@
+Thanks for your interest in Plotly.py!
+
+Before opening an issue, please search for existing and closed issues :)
+
+**Please** accompany bug reports with a reproducible example. Please use the [latest version](https://github.com/plotly/plotly.py/blob/master/CHANGELOG.md) of plotly.py in your report unless not applicable.
+
+Note that GitHub Issues are meant to be used for bug reports and feature requests only. Implementation or usage questions should be asked on [community.plotly.com](https://community.plotly.com/c/graphing-libraries/python/10) or on Stack Overflow (tagged [`plotly`](https://stackoverflow.com/questions/tagged/plotly)).

.github/pull_request_template.md

@@ -0,0 +1,38 @@
+<!--
+Please uncomment this block and take a look at this checklist if your PR is making substantial changes to **documentation**/impacts files in the `doc` directory. Check all that apply to your PR, and leave the rest unchecked to discuss with your reviewer! Not all boxes must be checked for every PR :)
+
+If your PR modifies code of the `plotly` package, we have a different checklist
+below :-).
+
+### Documentation PR
+
+- [ ] I've [seen the `doc/README.md` file](https://github.com/plotly/plotly.py/blob/master/doc/README.md)
+- [ ] This change runs in the current version of Plotly on PyPI and targets the `doc-prod` branch OR it targets the `master` branch
+- [ ] If this PR modifies the first example in a page or adds a new one, it is a `px` example if at all possible
+- [ ] Every new/modified example has a descriptive title and motivating sentence or paragraph
+- [ ] Every new/modified example is independently runnable
+- [ ] Every new/modified example is optimized for short line count	and focuses on the Plotly/visualization-related aspects of the example rather than the computation required to produce the data being visualized
+- [ ] Meaningful/relatable datasets are used for all new examples instead of randomly-generated data where possible
+- [ ] The random seed is set if using randomly-generated data in new/modified examples
+- [ ] New/modified remote datasets are loaded from https://plotly.github.io/datasets and added to https://github.com/plotly/datasets
+- [ ] Large computations are avoided in the new/modified examples in favour of loading remote datasets that represent the output of such computations
+- [ ] Imports are `plotly.graph_objects as go` / `plotly.express as px` / `plotly.io as pio`
+- [ ] Data frames are always called `df`
+- [ ] `fig = <something>` call is high up in each new/modified example (either `px.<something>` or `make_subplots` or `go.Figure`)
+- [ ] Liberal use is made of `fig.add_*` and `fig.update_*` rather than `go.Figure(data=..., layout=...)` in every new/modified example
+- [ ] Specific adders and updaters like `fig.add_shape` and `fig.update_xaxes` are used instead of big `fig.update_layout` calls in every new/modified example
+- [ ] `fig.show()` is at the end of each new/modified example
+- [ ] `plotly.plot()` and `plotly.iplot()` are not used in any new/modified example
+- [ ] Hex codes for colors are not used in any new/modified example in favour of [these nice ones](https://github.com/plotly/plotly.py/issues/2192)
+
+## Code PR
+
+- [ ] I have read through the [contributing notes](https://github.com/plotly/plotly.py/blob/master/CONTRIBUTING.md) and understand the structure of the package. In particular, if my PR modifies code of `plotly.graph_objects`, my modifications concern the `codegen` files and not generated files.
+- [ ] I have added tests (if submitting a new feature or correcting a bug) or
+  modified existing tests.
+- [ ] For a new feature, I have added documentation examples in an existing or
+  new tutorial notebook (please see the doc checklist as well).
+- [ ] I have added a CHANGELOG entry if fixing/changing/adding anything substantial.
+- [ ] For a new feature or a change in behaviour, I have updated the relevant docstrings in the code to describe the feature or behaviour (please see the doc checklist as well).
+
+-->

.gitignore

@@ -1,17 +1,65 @@
+0
+0.html
+iframe_figures/
+tests/test_orca/images/linux/failed/
+
 *.egg-info
 
 *.pyc
 
 *.gz
 
+*~
+
+doc/python/raw.githubusercontent.com/
+
+# Don't ignore dataset files
+!*.csv.gz
+!*.geojson.gz
+
 *.ipynb
 
 *.coverage
 
-build
+*.tox
+
+debug_script.py
+
+test_output.txt
+
+plotly/api/v2/spectacle_presentations.py
 
+plotly/presentation_objs/
+
+.idea
+
+node_modules/
+
+.pytest_cache
+
+# virtual envs
+vv
+venv*
+
+# dist files
+build
 dist
+plotly.egg-info/
 
-debug_script.py
+# macOS utility file
+**/.DS_Store
+
+tests/test_orca/images/*/failed
+tests/test_orca/images/*/tmp
+tests/test_core/test_offline/plotly.min.js
+temp-plot.html
+.vscode
+doc/python/.ipynb_checkpoints
+doc/python/.mapbox_token
+doc/.ipynb_checkpoints
+tags
+doc/check-or-enforce-order.py
+plotly/package_data/widgetbundle.js
 
-test_output.txt
+tests/percy/*.html
+tests/percy/pandas2/*.html