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: CONTRIBUTING.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,7 +144,9 @@ Please follow these steps to have your contribution considered by the maintainer
144
144
3. Follow all instructions in [the template](.github/PULL_REQUEST_TEMPLATE.md)
145
145
4. Follow the [engineering guidelines](./GUIDELINES.md).
146
146
5. Follow the [styleguides](#styleguides)
147
-
6. After you submit your pull request, verify that all [status checks](https://help.github.com/articles/about-status-checks/) are passing. <details><summary>What if the status checks are failing?</summary>
147
+
6. If the PR includes non-trivial changes, additions, or deletions (especially in Compact modules and/or witnesses),
148
+
add an entry to the [CHANGELOG](./CHANGELOG.md).
149
+
7. After you submit your pull request, verify that all [status checks](https://help.github.com/articles/about-status-checks/) are passing. <details><summary>What if the status checks are failing?</summary>
148
150
If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated.
149
151
A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.</details>
0 commit comments