open-index/open-npm huggingface dataset:
npm package: @gkalpak/ng-cla-check
Description: A utility for checking if an (AngularJS-related) GitHub PR has a signed CLA (based on its labels).
Author: gkalpak
Latest version: 0.2.4

# ng-cla-check [![Build Status][build-status-image]][build-status]

## Description

A utility for checking if an (AngularJS-related) GitHub PR has a signed CLA (based on its labels).

## Usage

### Using from the command-line

```shell
# Show version info
ng-cla-check --version

# Show usage instructions
ng-cla-check --usage

# Check a PR
ng-cla-check 12345
```

You can optionally specify the GitHub repo and/or CLA label to check for (by default
`angular/angular.js` and `cla: yes` respectively):

```shell
# Use non-default repo and CLA label
ng-cla-check 12345 --repo="some-user/some-repo" --claLabel="some text"
```

**Note:** To use a GitHub access-token, make it available in an environment variable named
`GITHUB_ACCESS_TOKEN`.

### Using from other modules

```js
let Checker = require('@gkalpak/ng-cla-check');
let checker = new Checker(/* Use default options */);

checker.check(prNo).then(
    () => {
      // CLA verified successfully.
    },
    err => {
      // Unable to verify CLA...
      if (err) {
        // ...because an error occurred (e.g. network error, authentication error, etc).
      } else {
        // ...because it was probably not signed.
      }
    });
```

You can also pass custom `ghToken`, `claLabel` or `repo` options:

```js
let checker = new Checker({
  ghToken: '...',   // Pass `false` to force anonymous (rate-limited) requests to the GitHub API.
  claLabel: 'some text',
  repo: 'some-user/some-repo'
});
```

**Note:** For convenience, the name of the GitHub access-token environment variable can be retrieved
with `Checker.getGhTokenVar()`.

Finally, you can prevent the `checker` from logging any messages to the console (e.g. warn when no
GitHub access-token is available), by passing `true` as the second argument:

```js
let quiet = true;
let checker = new Checker(null, quiet);
```

## Testing

The following test-types/modes are available:

- **Code-linting:** `npm run lint`
  _Lint JavaScript files using ESLint._

- **Unit tests:** `npm run test-unit`
  _Run all the unit tests once. These tests are quick and suitable to be run on every change._

- **E2E tests:** `npm run test-e2e`
  _Run all the end-to-end tests once. These test may hit actual API endpoints and are considerably
  slower than unit tests._

- **All tests:** `npm test` / `npm run test`
  _Run all of the above tests (code-linting, unit tests, e2e tests). This command is automatically
  run before `npm version` and `npm publish`._

- **"Watch" mode:** `npm run test-watch`
  _Watch all files and rerun the unit tests whenever something changes. For performance reasons,
  code-linting and e2e tests are omitted._


[build-status]: https://github.com/gkalpak/ng-cla-check/actions/workflows/ci.yml
[build-status-image]: https://github.com/gkalpak/ng-cla-check/actions/workflows/ci.yml/badge.svg?branch=master&event=push
npm package: @gkalpak/ng-maintain
Description: A collection of command-line utilities to help maintain (AngularJS-related) GitHub repositories.
Author: gkalpak
Latest version: 0.0.13

# ng-maintain [![Build Status][build-status-image]][build-status]

## Description

A collection of command-line utilities to help maintain (AngularJS-related) GitHub repositories.

## Usage

The following command-line tools are included:

- **ngm-cla-check:** [ng-cla-check][ng-cla-check]'s `ng-cla-check`.
- **ngm-diff-wh:** A `git diff` alternative based on [ng-maintain-utils][ng-maintain-utils]'
  `GitUtils.diffWithHighlight()`. See [ng-maintain-utils][ng-maintain-utils] for more info.
- **ngm-diff-wh2:** A `git diff` alternative based on [ng-maintain-utils][ng-maintain-utils]'
  `GitUtils.diffWithHighlight2()`. See [ng-maintain-utils][ng-maintain-utils] for more info.
- **ngm-pr-merge:** [ng-pr-merge][ng-pr-merge]'s `ng-pr-merge`.

## Testing

The following test-types/modes are available:

- **Code-linting:** `npm run lint`
  _Lint JavaScript files using ESLint._

- **Unit tests:** `npm run test-unit`
  _Run all the unit tests once. These tests are quick and suitable to be run on every change._

- **E2E tests:** `npm run test-e2e`
  _Run all the end-to-end tests once. These test may hit actual API endpoints or perform expensive
  I/O operations and are considerably slower than unit tests._

- **All tests:** `npm test` / `npm run test`
  _Run all of the above tests (code-linting, unit tests, e2e tests). This command is automatically
  run before `npm version` and `npm publish`._

- **"Watch" mode:** `npm run test-watch`
  _Watch all files and rerun the unit tests whenever something changes. For performance reasons,
  code-linting and e2e tests are omitted._


[build-status]: https://github.com/gkalpak/ng-maintain/actions/workflows/ci.yml
[build-status-image]: https://github.com/gkalpak/ng-maintain/actions/workflows/ci.yml/badge.svg?branch=master&event=push
[ng-cla-check]: https://www.npmjs.com/package/@gkalpak/ng-cla-check
[ng-maintain-utils]: https://www.npmjs.com/package/@gkalpak/ng-maintain-utils
[ng-pr-merge]: https://www.npmjs.com/package/@gkalpak/ng-pr-merge
npm package: @gkalpak/ng-pr-merge
Description: A utility for rebase-merging (AngularJS-related) GitHub PRs.
Author: gkalpak
Latest version: 0.0.36

# ng-pr-merge [![Build Status][build-status-image]][build-status]

_Warning:_
_This is still an experimental tool._
_Use at your own risk!_

## Description

A utility for rebase-merging (AngularJS-related) GitHub PRs.
Tasks performed:

1. Verify the CLA signature.
2. Fetch the PR as local branch.
3. Rebase and merge the local branch into the target branch (e.g. `master`).
4. Add `Closes #<PR>` to the commit message (at the right place).
5. Display the resulting changes for inspection (via `git diff` and `git log`).
   _(Experimental feature: Enhanced diff highlighting.)_
6. Interactively clean untracked files (e.g. auto-generated artifacts).
7. Run the CI-checks.
8. Push the changes to origin.
9. Clean everything up (e.g. if something goes wrong).

## Usage

Using in the command-line:

```shell
# Show version info
ng-pr-merge --version

# Show usage instructions
ng-pr-merge --usage

# Merge a PR
ng-pr-merge 12345
```

You can optionally specify the GitHub repo and/or branch to merge to (by default
`angular/angular.js` and `master` respectively):

```shell
# Use non-default repo and branch
ng-pr-merge 12345 --branch="some-branch" --repo="some-user/some-repo"
```

Finally, adding the `--instructions` argument, will display the commands that need to be run, but
not actually do anything. This is useful if you want to run the commands yourself:

```shell
# Only show instructions
ng-pr-merge 12345 [--branch="some-branch"] [--repo="some-user/some-repo"] --instructions
```

## Testing

The following test-types/modes are available:

- **Code-linting:** `npm run lint`
  _Lint JavaScript files using ESLint._

- **Unit tests:** `npm run test-unit`
  _Run all the unit tests once. These tests are quick and suitable to be run on every change._

- **E2E tests:** `npm run test-e2e`
  _Run all the end-to-end tests once. These test may hit actual API endpoints or perform expensive
  I/O operations and are considerably slower than unit tests._

- **All tests:** `npm test` / `npm run test`
  _Run all of the above tests (code-linting, unit tests, e2e tests). This command is automatically
  run before `npm version` and `npm publish`._

- **"Watch" mode:** `npm run test-watch`
  _Watch all files and rerun the unit tests whenever something changes. For performance reasons,
  code-linting and e2e tests are omitted._


[build-status]: https://github.com/gkalpak/ng-pr-merge/actions/workflows/ci.yml
[build-status-image]: https://github.com/gkalpak/ng-pr-merge/actions/workflows/ci.yml/badge.svg?branch=master&event=push