-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
14 changed files
with
719 additions
and
105 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
# Contributing | ||
|
||
## Development | ||
|
||
### Build | ||
|
||
After `yarn build/npm run build` command, you can see `thanks-contributors.[darwin|win32|linux].node` file in project root. This is the native addon built from [lib.rs](./src/lib.rs). | ||
|
||
### CI | ||
|
||
With GitHub actions, every commits and pull request will be built and tested automatically in [`node@14`, `@node16`] x [`macOS`, `Linux`, `Windows`] matrix. You will never be afraid of the native addon broken in these platforms. | ||
|
||
### Release | ||
|
||
Release native package is very difficult in old days. Native packages may ask developers who use its to install `build toolchain` like `gcc/llvm` , `node-gyp` or something more. | ||
|
||
With `GitHub actions`, we can easily prebuild `binary` for major platforms. And with `N-API`, we should never afraid of **ABI Compatible**. | ||
|
||
The other problem is how to deliver prebuild `binary` to users. Download it in `postinstall` script is a common way which most packages do it right now. The problem of this solution is it introduced many other packages to download binary which has not been used by `runtime codes`. The other problem is some user may not easily download the binary from `GitHub/CDN` if they are behind private network (But in most case, they have a private NPM mirror). | ||
|
||
In this package we choose a better way to solve this problem. We release different `npm packages` for different platform. And add it to `optionalDependencies` before release the `Major` package to npm. | ||
|
||
`NPM` will choose which native package should download from `registry` automatically. You can see [npm](./npm) dir for details. And you can also run `yarn add @napi-rs/thanks-contributors` to see how it works. | ||
|
||
### Develop requirements | ||
|
||
- Install latest `Rust` | ||
- Install `Node.js@14+` which fully supported `Node-API` | ||
- Install `[email protected]` | ||
|
||
### Test in local | ||
|
||
- `yarn` | ||
- `yarn build:debug` | ||
- `node bin.js --help` | ||
|
||
### Release package | ||
|
||
Ensure you have set you **NPM_TOKEN** in `GitHub` project setting. | ||
|
||
In `Settings -> Secrets`, add **NPM_TOKEN** into it. | ||
|
||
When you want release package: | ||
|
||
``` | ||
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=<prerelease-id>] | from-git] | ||
git push | ||
``` | ||
|
||
GitHub actions will do the rest job for you. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -62,53 +62,3 @@ If the url can't be found only the name will be printed. | |
## Caveats | ||
- Getting the PR number only works if you consistently add the number in the commit itself, e.g. in `feat: My cool feature (#123)`. This automatically happens in GitHub's UI if you use squash commits. | ||
## Development | ||
### Build | ||
After `yarn build/npm run build` command, you can see `thanks-contributors.[darwin|win32|linux].node` file in project root. This is the native addon built from [lib.rs](./src/lib.rs). | ||
### CI | ||
With GitHub actions, every commits and pull request will be built and tested automatically in [`node@14`, `@node16`] x [`macOS`, `Linux`, `Windows`] matrix. You will never be afraid of the native addon broken in these platforms. | ||
### Release | ||
Release native package is very difficult in old days. Native packages may ask developers who use its to install `build toolchain` like `gcc/llvm` , `node-gyp` or something more. | ||
With `GitHub actions`, we can easily prebuild `binary` for major platforms. And with `N-API`, we should never afraid of **ABI Compatible**. | ||
The other problem is how to deliver prebuild `binary` to users. Download it in `postinstall` script is a common way which most packages do it right now. The problem of this solution is it introduced many other packages to download binary which has not been used by `runtime codes`. The other problem is some user may not easily download the binary from `GitHub/CDN` if they are behind private network (But in most case, they have a private NPM mirror). | ||
In this package we choose a better way to solve this problem. We release different `npm packages` for different platform. And add it to `optionalDependencies` before release the `Major` package to npm. | ||
`NPM` will choose which native package should download from `registry` automatically. You can see [npm](./npm) dir for details. And you can also run `yarn add @napi-rs/thanks-contributors` to see how it works. | ||
### Develop requirements | ||
- Install latest `Rust` | ||
- Install `Node.js@14+` which fully supported `Node-API` | ||
- Install `[email protected]` | ||
### Test in local | ||
- `yarn` | ||
- `yarn build:debug` | ||
- `node bin.js --help` | ||
### Release package | ||
Ensure you have set you **NPM_TOKEN** in `GitHub` project setting. | ||
In `Settings -> Secrets`, add **NPM_TOKEN** into it. | ||
When you want release package: | ||
``` | ||
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=<prerelease-id>] | from-git] | ||
git push | ||
``` | ||
GitHub actions will do the rest job for you. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
import { invokeCli } from "../vitest.utils" | ||
|
||
describe(`cli`, () => { | ||
it(`should show help command`, () => { | ||
const { exitCode, stdout } = invokeCli([`--help`]) | ||
|
||
expect(stdout).toMatchInlineSnapshot(` | ||
"This little script accesses GitHub's API to get all contributors and their PRs between two distinct | ||
points in the history of commits. This is helpful for changelogs where you'd want to list all | ||
contributions for that release (so e.g. changes between v1 and v1.1). | ||
Usage: @lekoarts/thanks-contributors [OPTIONS] <BASE> <HEAD> [OWNER] [REPO] | ||
Arguments: | ||
<BASE> | ||
Pointer from where to start looking for changes | ||
<HEAD> | ||
Pointer until where to stop looking for changes | ||
[OWNER] | ||
Name of the owner/user/organization of the repository | ||
[default: gatsbyjs] | ||
[REPO] | ||
Name of the repository | ||
[default: gatsby] | ||
Options: | ||
-i, --include-org-members <INCLUDE_ORG_MEMBERS> | ||
Include organization members into the list [default: false] | ||
[possible values: true, false] | ||
-e, --excludes <EXCLUDES>... | ||
List of members to exclude from the list. Usage: -e=member1,member2 [default: | ||
\\"renovate-bot\\", \\"renovate[bot]\\"] | ||
-h, --help | ||
Print help information (use \`-h\` for a summary)" | ||
`) | ||
expect(exitCode).toBe(0) | ||
}) | ||
}) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.