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: docs/community/documentation.md
+3-4
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ flowchart LR
42
42
You can use `note`, `tip`, `warning` and `danger` in triple backticks to add a note, tip, warning or danger box.
43
43
Do not use vitepress specific markdown syntax `::: warning` as it will not be processed correctly.
44
44
45
-
````
45
+
````markdown
46
46
```note
47
47
Note content
48
48
```
@@ -58,11 +58,10 @@ Warning content
58
58
```danger
59
59
Danger content
60
60
```
61
-
62
61
````
63
62
64
63
> **Note**
65
-
> If the change is _only_ to the documentation, you can get your changes published to the site quicker by making a PR to the `master` branch.
64
+
> If the change is _only_ to the documentation, you can get your changes published to the site quicker by making a PR to the `master` branch. In that case, your branch should be based on master, not develop.
66
65
67
66
We encourage contributions to the documentation at [packages/mermaid/src/docs in the _develop_ branch](https://github.com/mermaid-js/mermaid/tree/develop/packages/mermaid/src/docs).
68
67
@@ -87,7 +86,7 @@ _\[TODO: need to keep this in sync with [check out a git branch in Contributing
87
86
2. Find the Markdown file (.md) to edit in the `packages/mermaid/src/docs` directory.
88
87
3. Make changes or add new documentation.
89
88
4. Commit changes to your branch and push it to GitHub (which should create a new branch).
90
-
5. Create a Pull Request of your fork.
89
+
5. Create a Pull Request from the branch of your fork.
Copy file name to clipboardExpand all lines: docs/community/questions-and-suggestions.md
+1-3
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
>
3
3
> ## THIS IS AN AUTOGENERATED FILE. DO NOT EDIT.
4
4
>
5
-
> ## Please edit the corresponding file in [/packages/mermaid/src/docs/community/questionsAndSuggestions.md](../../packages/mermaid/src/docs/community/questionsAndSuggestions.md).
5
+
> ## Please edit the corresponding file in [/packages/mermaid/src/docs/community/questions-and-suggestions.md](../../packages/mermaid/src/docs/community/questions-and-suggestions.md).
6
6
7
7
# Questions or Suggestions?
8
8
@@ -24,5 +24,3 @@ Feel free to add to the discussion on the issue or topic.
24
24
If you can't find anything that already addresses your question or suggestion, _open a new issue:_
25
25
26
26
Log in to [GitHub.com](https://www.github.com), open or append to an issue [using the GitHub issue tracker of the mermaid-js repository](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Area%3A+Documentation%22).
[](https://github.com/mermaid-js/mermaid/actions/workflows/build.yml)
@@ -343,7 +349,9 @@ Don't hesitate to contact me if you want to get involved!
343
349
344
350
<divclass='badges'>
345
351
346
-
[](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%21%22)[](https://github.com/mermaid-js/mermaid/graphs/contributors)[](https://github.com/mermaid-js/mermaid/graphs/contributors)
352
+
[](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%21%22)
Copy file name to clipboardExpand all lines: packages/mermaid/src/docs/community/documentation.md
+3-4
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ flowchart LR
28
28
You can use `note`, `tip`, `warning` and `danger` in triple backticks to add a note, tip, warning or danger box.
29
29
Do not use vitepress specific markdown syntax `::: warning` as it will not be processed correctly.
30
30
31
-
````
31
+
````markdown
32
32
```note
33
33
Note content
34
34
```
@@ -44,11 +44,10 @@ Warning content
44
44
```danger
45
45
Danger content
46
46
```
47
-
48
47
````
49
48
50
49
```note
51
-
If the change is _only_ to the documentation, you can get your changes published to the site quicker by making a PR to the `master` branch.
50
+
If the change is _only_ to the documentation, you can get your changes published to the site quicker by making a PR to the `master` branch. In that case, your branch should be based on master, not develop.
52
51
```
53
52
54
53
We encourage contributions to the documentation at [packages/mermaid/src/docs in the _develop_ branch](https://github.com/mermaid-js/mermaid/tree/develop/packages/mermaid/src/docs).
@@ -74,7 +73,7 @@ _[TODO: need to keep this in sync with [check out a git branch in Contributing C
74
73
2. Find the Markdown file (.md) to edit in the `packages/mermaid/src/docs` directory.
75
74
3. Make changes or add new documentation.
76
75
4. Commit changes to your branch and push it to GitHub (which should create a new branch).
77
-
5. Create a Pull Request of your fork.
76
+
5. Create a Pull Request from the branch of your fork.
Copy file name to clipboardExpand all lines: packages/mermaid/src/docs/community/questions-and-suggestions.md
-2
Original file line number
Diff line number
Diff line change
@@ -18,5 +18,3 @@ Feel free to add to the discussion on the issue or topic.
18
18
If you can't find anything that already addresses your question or suggestion, _open a new issue:_
19
19
20
20
Log in to [GitHub.com](https://www.github.com), open or append to an issue [using the GitHub issue tracker of the mermaid-js repository](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Area%3A+Documentation%22).
[](https://github.com/mermaid-js/mermaid/actions/workflows/build.yml)
@@ -120,7 +126,9 @@ Don't hesitate to contact me if you want to get involved!
120
126
121
127
<divclass='badges'>
122
128
123
-
[](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%21%22)[](https://github.com/mermaid-js/mermaid/graphs/contributors)[](https://github.com/mermaid-js/mermaid/graphs/contributors)
129
+
[](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%21%22)
0 commit comments