Skip to content

Commit d086c61

Browse files
authored
Merge pull request #95 from asmeurer/checkboxes
Use checkboxes for the releasing docs
2 parents b6cd7e9 + b7d5bad commit d086c61

File tree

3 files changed

+22
-7
lines changed

3 files changed

+22
-7
lines changed

docs/_static/custom.css

+14
Original file line numberDiff line numberDiff line change
@@ -10,3 +10,17 @@ body {
1010
html {
1111
scroll-behavior: auto;
1212
}
13+
14+
/* Make checkboxes from the tasklist extension ('- [ ]' in Markdown) not add bullet points to the checkboxes.
15+
16+
This can be removed once https://github.com/executablebooks/mdit-py-plugins/issues/59 is addressed.
17+
*/
18+
19+
.contains-task-list {
20+
list-style: none;
21+
}
22+
23+
/* Make the checkboxes indented like they are bullets */
24+
.task-list-item-checkbox {
25+
margin: 0 0.2em 0.25em -1.4em;
26+
}

docs/conf.py

+2-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,8 @@
3636
templates_path = ['_templates']
3737
exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
3838

39-
myst_enable_extensions = ["dollarmath", "linkify"]
39+
myst_enable_extensions = ["dollarmath", "linkify", "tasklist"]
40+
myst_enable_checkboxes = True
4041

4142
napoleon_use_rtype = False
4243
napoleon_use_param = False

docs/releasing.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22

33
To release array-api-strict:
44

5-
- Create a release branch and make a PR on GitHub.
5+
- [ ] Create a release branch and make a PR on GitHub.
66

7-
- Update `changelog.md` with the changes for the release.
7+
- [ ] Update `changelog.md` with the changes for the release.
88

9-
- Make sure the CI is passing on the release branch PR. Also double check that
9+
- [ ] Make sure the CI is passing on the release branch PR. Also double check that
1010
you have properly pulled `main` and merged it into the release branch so
1111
that the branch contains all the necessary changes for the release.
1212

13-
- When you are ready to make the release, create a tag with the release number
13+
- [ ] When you are ready to make the release, create a tag with the release number
1414

1515
```
1616
git tag -a 2.2 -m "array-api-strict 2.2"
@@ -30,8 +30,8 @@ To release array-api-strict:
3030
in the package metadata is all automatically computed from the tag, so it is
3131
not necessary to update the version anywhere else.
3232

33-
- Once the release is published, you can merge the PR.
33+
- [ ] Once the release is published, you can merge the PR.
3434

35-
- The conda-forge bot will automatically send a PR to the
35+
- [ ] The conda-forge bot will automatically send a PR to the
3636
[array-api-strict-feedstock](https://github.com/conda-forge/array-api-strict-feedstock)
3737
updating the version, which you should merge.

0 commit comments

Comments
 (0)