File tree 1 file changed +23
-0
lines changed
1 file changed +23
-0
lines changed Original file line number Diff line number Diff line change @@ -5,6 +5,29 @@ It uses automation and as few steps as possible to get things done.
5
5
6
6
If you are comfortable with and prefer a more manual setup refer to the [ ] ( topics/manual-dev.md ) section.
7
7
8
+ ## Testing pre-release and nightly
9
+
10
+ You can test the alpha, beta
11
+ and release candidates of pydata sphinx theme on your your projects. To do so
12
+ simply install with pip using the ` --pre ` flag:
13
+
14
+ ``` console
15
+ $ pip install --pre pydata-sphinx-theme
16
+ ```
17
+
18
+ If an ` alpha ` , ` beta ` or ` rc ` is available, pip will install it.
19
+
20
+ You can use the ` --pre ` flag in your project's continuous integration test suite
21
+ to catch regressions or bugs before their release.
22
+
23
+ If you are even more adventurous pydata-sphinx-theme has nightly builds, you can try following the
24
+ instructions provided [ on the scientific-python/upload-nightly-action
25
+ Readme] ( https://github.com/scientific-python/upload-nightly-action?tab=readme-ov-file#using-nightly-builds-in-ci )
26
+ on installing nightly wheels.
27
+
28
+ Installing nightly wheels in your project's CI jobs is a great way to help theme developers catch bugs ahead of
29
+ time.
30
+
8
31
## Workflow for contributing changes
9
32
10
33
We follow a [ typical GitHub workflow] ( https://guides.github.com/introduction/flow/ )
You can’t perform that action at this time.
0 commit comments