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
args: comment "Hey! Thanks for opening the issue. Can you provide more information about the issue? Please fill the issue template when opening the issue without deleting any section. We need all the information we can, to be able to help. Make sure to at least provide - Current behaviour, Expected behaviour, A way to reproduce the issue with minimal code (link to [snack.expo.io](https://snack.expo.io)) or a repo on GitHub, and the information about your environment (such as the platform of the device, versions of all the packages etc.)."
17
+
18
+
needs-repro:
19
+
runs-on: ubuntu-latest
20
+
if: github.event.label.name == 'needs repro'
21
+
steps:
22
+
- uses: actions/checkout@master
23
+
- uses: actions/github@v1.0.0
24
+
env:
25
+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
26
+
with:
27
+
args: comment "Hey! Thanks for opening the issue. Can you provide a minimal repro which demonstrates the issue? Posting a snippet of your code in the issue is useful, but it's not usually straightforward to run. A repro will help us debug the issue faster. Please try to keep the repro as small as possible. The easiest way to provide a repro is on [snack.expo.io](https://snack.expo.io). If it's not possible to repro it on [snack.expo.io](https://snack.expo.io), then you can also provide the repro in a GitHub repository."
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Code of Conduct
4
4
5
-
We want this community to be friendly and respectful to each other. Please read [the full text](/CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
5
+
We want this community to be friendly and respectful to each other. Please read [the full text](https://callstack.com/code-of-conduct/?utm_source=github.com&utm_medium=referral&utm_campaign=react-native-paper&utm_term=code-of-conduct) so that you can understand what actions will and will not be tolerated.
6
6
7
7
## Our Development Process
8
8
@@ -32,19 +32,18 @@ Our pre-commit hooks verify that your commit message matches this format when co
32
32
33
33
### Linting and tests
34
34
35
-
We use `flow` for type checking, `eslint` with `prettier` for linting and formatting the code, and `jest` for testing. Our pre-commit hooks verify that the linter and tests pass when commiting. You can also run the following commands manually:
35
+
We use `typescript` for type checking, `eslint` with `prettier` for linting and formatting the code, and `jest` for testing. Our pre-commit hooks verify that the linter and tests pass when commiting. You can also run the following commands manually:
36
36
37
-
*`yarn flow`: run flow on all files.
38
-
*`yarn typescript`: run tests for typescript definitions.
39
-
*`yarn lint`: lint files with eslint and prettier.
40
-
*`yarn test`: run unit tests with jest.
37
+
*`yarn typescript`: type-check files with `tsc`.
38
+
*`yarn lint`: lint files with `eslint` and `prettier`.
39
+
*`yarn test`: run unit tests with `jest`.
41
40
42
41
### Sending a pull request
43
42
44
43
When you're sending a pull request:
45
44
46
45
* Prefer small pull requests focused on one change.
47
-
* Verify that `flow`, `eslint` and all tests are passing.
46
+
* Verify that `typescript`, `eslint` and all tests are passing.
48
47
* Preview the documentation to make sure it looks good.
49
48
* Follow the pull request template when opening a pull request.
50
49
@@ -65,7 +64,7 @@ To run the example on web, run `yarn example web` in the project root.
65
64
66
65
### Working on documentation
67
66
68
-
The documentation is automatically generated from the [flowtype](https://flowtype.org) annotations in the components. You can add comments above the type annotations to add descriptions. To preview the generated documentation, run `yarn docs start` in the project root.
67
+
The documentation is automatically generated from the [TypeScript](https://www.typescriptlang.org/) annotations in the components. You can add comments above the type annotations to add descriptions. To preview the generated documentation, run `yarn docs start` in the project root.
0 commit comments