Merge pull request #9 from OpenAstronomy/dependabot/npm_and_yarn/vercel/ncc-0.27.0

Bump @vercel/ncc from 0.26.1 to 0.27.0

Author: pllim

README.md

@@ -20,7 +20,7 @@ skip CI for that PR.
 *Note: If GitHub Actions ever supports this feature natively for pull requests,
 then we do not need this action.*
 
-#### Ways to customize
+## Ways to customize
 
 The behavior described above is the default, but it could be customized
 using these options (also see examples below):
@@ -32,7 +32,7 @@ using these options (also see examples below):
   Instead, it would set an output value for `run_next` to `true` or `false`
   to be used by downstream jobs.
 
-#### Examples
+## Examples
 
 Here are some simple examples to use this action in your workflows.
 
@@ -53,7 +53,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Fail means CI is skipped on purpose
-      uses: pllim/action-skip-ci@main
+      uses: OpenAstronomy/action-skip-ci@main
       with:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
@@ -87,7 +87,7 @@ jobs:
       run_next: ${{ steps.skip_ci_step.outputs.run_next }}
     steps:
     - name: Set output to skip CI
-      uses: pllim/action-skip-ci@main
+      uses: OpenAstronomy/action-skip-ci@main
       id: skip_ci_step
       with:
         NO_FAIL: true
@@ -102,9 +102,24 @@ jobs:
     ...
 ```
 
-#### Why does this action not cancel workflow instead of failing?
+## Why does this action not cancel workflow instead of failing?
 
 This is because cancelling the workflow does not work when the command
 is issued from a pull request opened from a fork due to lack of
 write access from the fork's GitHub token. The cancellation does not
 fail but nothing gets cancelled anyway.
+
+## For developers
+
+To install/update dependencies:
+
+    npm install
+
+To build:
+
+    npm run build
+
+To run it locally (might require tinkering with `src/main.ts` to mock
+the GitHub events):
+
+    node dist/index.js