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
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,17 +99,13 @@ Please open an issue with a proposal for a new feature or refactoring before sta
99
99
3. If you've changed APIs, update the documentation.
100
100
4. Ensure the tests pass (`npm run test`).
101
101
102
-
You should see a pre-commit hook run before each commit. If it does not, you may need to reset you Git hookspath:
103
-
104
-
```
105
-
git config --unset core.hookspath
106
-
```
102
+
You should see a pre-commit hook run before each commit.
107
103
108
104
You can now submit a pull request, referencing any issues it addresses.
109
105
110
106
Please try to keep your pull request focused in scope and avoid including unrelated commits.
111
107
112
-
After you have submitted your pull request, we'll try to get back to you as soon as possible. We may suggest some changes or improvements.
108
+
After you have submitted your pull request, it's recommended that **you** perform the first code review. We'll try to get back to you as soon as possible and may suggest changes.
113
109
114
110
Thank you for contributing!
115
111
@@ -118,7 +114,7 @@ Thank you for contributing!
118
114
To commit, publish, and push a final version:
119
115
120
116
```
121
-
npm run release -- <version>
117
+
npm run release -- <version> --opt=<opt-code>
122
118
```
123
119
124
120
Release candidates or versions that you'd like to publish to npm, but do not want to produce a commit and push it to GitHub:
Add an event handler that is called with `{colorScheme: "dark" | "light"}` when appearance preferences change. Returns a `remove` method used to remove the change listener.
You can use the Appearance module to determine if the user prefers a dark color scheme. Although the color scheme is available immediately, this may change (e.g. scheduled color scheme change at sunrise or sunset). Any rendering logic or styles that depend on the user preferred color scheme should try to call this function on every render, rather than caching the value.
When `true`, the scroll view automatically centers the content when the content is smaller than the scroll view bounds; when the content is larger than the scroll view, this property has no effect.
When `true`, the default `PanResponder` on the `ScrollView` is disabled, and full control over pointers inside the `ScrollView` is left to its child components. This is meant to be used when native "snap-to" scrolling behavior is needed.
0 commit comments