Commit f4e736b

1. Download and install Node.js 12.x, which includes npm.

https://nodejs.org/en/download/current/

1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."

cd hello-world-javascript-action

```

```shell

npm init -y

```

name: 'Hello World'

description: 'Greet someone and record the time'

core.setFailed(error.message);

If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."

- Environment variables the action uses.

- An example of how to use your action in a workflow.

git add action.yml index.js node_modules/* package.json package-lock.json README.md

git commit -m "My first action is ready"

git push --follow-tags

git add action.yml dist/index.js node_modules/*

git commit -m "Use vercel/ncc"

git push --follow-tags

{% raw %}

on: [push]

steps:

- name: Hello world action step

id: hello

with:

who-to-greet: 'Mona the Octocat'

# Use the output from the `hello` step

If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."

You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.

In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."


If you run any of the commands for ignoring dependencies or versions, {% data variables.product.prodname_dependabot %} stores the preferences for the repository centrally. While this is a quick solution, for repositories with more than one contributor it is better to explicitly define the dependencies and versions to ignore in the configuration file. This makes it easy for all contributors to see why a particular dependency isn't being updated automatically. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)."

title: Searching for information on GitHub

redirect_from:

- /categories/78/articles/

- /categories/search/

- /getting-started-with-searching-on-github

- /searching-on-github

```shell

/Users/hubot/.gnupg/secring.gpg

------------------------------------

sec 4096R/<em>3AA5C34371567BD2</em> 2016-03-10 [expires: 2017-03-10]

```shell

{% note %}