3
3
Interested in contributing to the Material theme? Want to report a bug? Before
4
4
you do, make sure to sign the[ CLA] [ 5 ] and please read the following guidelines.
5
5
6
- [ 5 ] : https://google.com
6
+ [ 5 ] : https://servicebot.io/cla
7
7
8
8
## Submission context
9
9
@@ -50,8 +50,7 @@ readily available.
50
50
51
51
We want to fix all the issues as soon as possible, but before fixing a bug we
52
52
need to reproduce and confirm it. In order to reproduce bugs we will
53
- systematically ask you to provide a minimal reproduction scenario using the
54
- custom issue template. Please stick to the issue template.
53
+ systematically ask you to provide a minimal reproduction scenario.
55
54
56
55
Unfortunately we are not able to investigate / fix bugs without a minimal
57
56
reproduction scenario, so if we don't hear back from you we may close the issue.
@@ -62,7 +61,7 @@ Search GitHub for an open or closed PR that relates to your submission. You
62
61
don't want to duplicate effort. If you do not find a related issue or PR,
63
62
go ahead.
64
63
65
- 1 . ** Development** : Fork the project, set up the [ development environment ] [ 4 ] ,
64
+ 1 . ** Development** : Fork the project,
66
65
make your changes in a separate git branch and add descriptive messages to
67
66
your commits.
68
67
@@ -78,4 +77,3 @@ go ahead.
78
77
After your PR is merged, you can safely delete your branch and pull the changes
79
78
from the main (upstream) repository.
80
79
81
- [ 4 ] : http://squidfunk.github.io/mkdocs-material/customization/#theme-development
0 commit comments