You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributing.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,7 +224,30 @@ the `plotly/plotly.js` GitHub repository (and place them in
224
224
`plotly/package_data`). It will then regenerate all of the `graph_objs`
225
225
classes based on the new schema.
226
226
227
-
For dev branches, it is also possible to use `updateplotlyjsdev --devrepo reponame --devbranch branchname` to update to development versions of `plotly.js`. This will fetch the `plotly.js` in the CircleCI artifact of the branch `branchname` of the repo `reponame`. If `--devrepo` or `--devbranch` are omitted, `updateplotlyjsdev` defaults using `plotly/plotly.js` and `master` respectively.
227
+
For dev branches, it is also possible to use `updateplotlyjsdev` in two configurations:
228
+
229
+
### CircleCI Release
230
+
231
+
If your devbranch is part of the official plotly.js repository, you can use
to update to development versions of `plotly.js`. This will fetch the `plotly.js` in the CircleCI artifact of the branch `branchname` of the repo `reponame`. If `--devrepo` or `--devbranch` are omitted, `updateplotlyjsdev` defaults using `plotly/plotly.js` and `master` respectively.
236
+
237
+
### Local Repository
238
+
239
+
If you have a local repository of `plotly.js` you'd like to try, you can run:
240
+
241
+
```bash
242
+
# In your plotly.js/ directory, prepare the package:
243
+
244
+
$ npm run build
245
+
$ npm pack
246
+
$ mv plotly.js-*.tgz plotly.js.tgz
247
+
248
+
# In your plotly.py/packages/python/plotly/ directory:
0 commit comments