actions/setup-python
actions/setup-python
3
0
Fork 0
mirror of https://gitea.com/actions/setup-python.git synced 2024-11-21 17:49:35 +01:00
Code Issues Projects Activity Pipelines

Spelling & grammar

Browse source
This commit is contained in:
Brian Cristante 2019-12-27 11:26:49 -05:00
parent 11c9de6408
commit d0da811f3d
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/contributors.md
View file

@ -2,9 +2,9 @@
### Checkin
- Do checkin source (src)
- Do checkin a single index.js file after running `ncc`
- Do not checkin node_modules
- Do check in source (src)
- Do check in a single index.js file after running `ncc`
- Do not check in node_modules
### NCC
@ -12,7 +12,7 @@ In order to avoid uploading `node_modules` to the repository, we use [zeit/ncc](
### Developing
If you're developing locally you can run
If you're developing locally, you can run
```
npm install
tsc
@ -24,7 +24,7 @@ During the commit step, Husky will take care of formatting all files with [Prett
### Testing
We ask that you include a link to a succesfull run that utilizes the changes you are working on. For example, if your changes are in the branch `newAwesomeFeature`, then show an example run that uses `setup-python@newAwesomeFeature` or `my-fork@newAwesomeFeature`. This will help speed up testing and help us confirm that there are no breaking changes or bugs.
We ask that you include a link to a successful run that utilizes the changes you are working on. For example, if your changes are in the branch `newAwesomeFeature`, then show an example run that uses `setup-python@newAwesomeFeature` or `my-fork@newAwesomeFeature`. This will help speed up testing and help us confirm that there are no breaking changes or bugs.
### Releases