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: .github/CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ The labels can only be set and modified by committers.
66
66
67
67
### Issue Reporting Disclaimer
68
68
69
-
We want to improve the quality of github-docs-cookiecutter and good bug reports are welcome! But our capacity is limited, thus we reserve the right to close or to not process insufficient bug reports in favor of those which are very cleanly documented and easy to reproduce. Even though we would like to solve each well-documented issue, there is always the chance that it will not happen - remember: github-docs-cookiecutter is Open Source and comes without warranty.
69
+
We want to improve the quality of, github-docs-cookiecutter, and good bug reports are welcome! But our capacity is limited, thus we reserve the right to close or to not process insufficient bug reports in favor of those which are very cleanly documented and easy to reproduce. Even though we would like to solve each well-documented issue, there is always the chance that it will not happen - remember: github-docs-cookiecutter is Open Source and comes without warranty.
70
70
71
71
Bug report analysis support is very welcome! (e.g. pre-analysis or proposing solutions)
72
72
@@ -117,7 +117,7 @@ These are some of the rules we try to follow:
117
117
*```Fixes #(issueNumber)```
118
118
* Do NOT add a colon after "Fixes" - this prevents automatic closing.
119
119
6. Create a Pull Request
120
-
7. Follow the link posted by the github-docs-cookiecutter to your pull request and accept it, as described in detail above.
120
+
7. Follow the link posted by the, github-docs-cookiecutter, project to your pull request and accept it, as described in detail above.
121
121
8. Wait for our code review and approval, possibly enhancing your change on request
122
122
* Note that the github-docs-cookiecutter developers also have their regular duties, so depending on the required effort for reviewing, testing and clarification this may take a while
123
123
9. Once the change has been approved we will inform you in a comment
Copy file name to clipboardExpand all lines: .github/SECURITY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Security Vulnerabilities
2
2
3
-
The github-docs-cookiecutter is built with security and data privacy in mind to ensure your data is safe.
3
+
The github-docs-cookiecutter project is built with security and data privacy in mind to ensure your data is safe.
4
4
5
5
## Reporting
6
6
We are grateful for security researchers and users reporting a vulnerability to us, first. To ensure that your request is handled in a timely manner and non-disclosure of vulnerabilities can be assured, please follow the below guideline.
Copy file name to clipboardExpand all lines: docs/jekyll/_manual/contribute/create-feature-request.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,9 @@ We're excited to hear your ideas! Before you submit a feature request, consider
19
19
20
20
When you're ready to submit a feature request, use the [feature request template](https://github.com/jcook3701/github-docs-cookiecutter/issues/new?template=02-feature_request.md). The template has three sections that help maintainers understand what you need and why.
21
21
22
-
<!-- Here's an [example of how all three sections work together in an actual feature request](https://github.com/jcook3701/github-docs-cookiecutter) from the github-docs-cookiecutter community. We'll analyze each section based on this example feature request. -->
22
+
<!-- TODO: Put together an example feature request.
23
+
24
+
Here's an [example of how all three sections work together in an actual feature request](https://github.com/jcook3701/github-docs-cookiecutter) from the github-docs-cookiecutter community. We'll analyze each section based on this example feature request. -->
23
25
24
26
## Best practices for feature requests
25
27
@@ -52,6 +54,6 @@ After submitting your feature request, monitor the discussion. Answer questions
52
54
53
55
## Contributing the feature yourself
54
56
55
-
If you want to implement the feature yourself, feel free to create a pull request following the [pull request guidelines](create-pull-request.md).
57
+
If you want to implement the feature yourself, feel free to create a pull request following the [pull request guidelines]({% link create-pull-request.md %}).
56
58
57
59
We welcome community contributions and appreciate your help making github-docs-cookiecutter better!
0 commit comments