8000 Update terminology in setup-python by brcrista · Pull Request #46 · actions/setup-python · GitHub
[go: up one dir, main page]

Skip to content

Update terminology in setup-python #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Dec 30, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Spelling & grammar
  • Loading branch information
brcrista committed Dec 27, 2019
commit d0da811f3d9eee1e43b47e1812b611faee1088a3
10 changes: 5 additions & 5 deletions docs/contributors.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,17 @@

### 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

In order to avoid uploading `node_modules` to the repository, we use [zeit/ncc](https://github.com/zeit/ncc) to create a single `index.js` file that gets saved in `dist/`.

### Developing

If you're developing locally you can run
If you're developing locally, you can run
```
npm install
tsc
Expand All @@ -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

Expand Down
0