Files

79 lines
2.5 KiB
Markdown
Raw Permalink Normal View History

2022-03-02 12:39:59 -05:00
# actions/add-to-project
2022-01-31 14:09:42 -05:00
2022-02-01 22:20:12 +00:00
🚨 **This action is a work in progress. Please do not use it except for
experimentation until a release has been prepared.** 🚨
2022-01-31 14:09:42 -05:00
2022-02-01 22:19:35 +00:00
Use this action to automatically add issues to a GitHub Project. Note that this
is for [GitHub Projects
(beta)](https://docs.github.com/en/issues/trying-out-the-new-projects-experience/about-projects),
not the original GitHub Projects.
To use the action, create a workflow that runs when issues are opened in your
repository. Run this action in a step, optionally configuring any filters you
may want to add, such as only adding issues with certain labels.
2022-01-31 14:09:42 -05:00
```yaml
2022-02-01 22:19:35 +00:00
name: Add bugs to bugs project
2022-01-31 14:09:42 -05:00
on:
2022-02-01 22:19:35 +00:00
issues:
types:
- opened
2022-01-31 14:09:42 -05:00
jobs:
add-to-project:
name: Add issue to project
runs-on: ubuntu-latest
steps:
2022-03-02 12:24:18 -05:00
# Pointing to a branch name generally isn't the safest way to refer to an action,
# but this is how you can use this action now before we've begun creating releases.
2022-03-02 12:24:57 -05:00
# Another option would be to point to a full commit SHA.
2022-03-02 12:24:18 -05:00
- uses: actions/add-to-project@main
2022-01-31 14:09:42 -05:00
with:
project-url: https://github.com/orgs/<orgName>/projects/<projectNumber>
github-token: ${{ secrets.ADD_TO_PROJECT_PAT }}
2022-01-31 15:46:31 -05:00
labeled: bug
2022-01-31 14:09:42 -05:00
```
2022-02-01 22:19:35 +00:00
## Inputs
2022-01-31 14:09:42 -05:00
2022-02-01 22:19:35 +00:00
- `project-url` is the URL of the GitHub Project to add issues to.
- `github-token` is a [personal access
token](https://github.com/settings/tokens/new) with the `repo`, `write:org` and
`read:org` scopes.
- `labeled` is a comma-separated list of labels. For an issue to be added to the
project, it must have _one_ of the labels in the list. Omitting this key means
that all issues will be added.
2022-01-31 15:46:31 -05:00
2022-02-01 22:19:35 +00:00
## Development
2022-01-31 14:09:42 -05:00
2022-02-01 22:19:35 +00:00
To get started contributing to this project, clone it and install dependencies.
2022-02-16 10:15:42 -05:00
Note that this action runs in Node.js 16.x, so we recommend using that version
2022-02-01 22:19:35 +00:00
of Node (see "engines" in this action's package.json for details).
2022-01-31 14:09:42 -05:00
2022-02-01 22:19:35 +00:00
```shell
> git clone https://github.com/actions/add-to-project
> cd add-to-project
> npm install
2022-01-31 14:09:42 -05:00
```
2022-02-01 22:19:35 +00:00
Or, use [GitHub Codespaces](https://github.com/features/codespaces).
2022-01-31 15:38:31 -05:00
2022-02-01 22:19:35 +00:00
See the [toolkit
documentation](https://github.com/actions/toolkit/blob/master/README.md#packages)
for the various packages used in building this action.
2022-01-31 14:09:42 -05:00
## Publish to a distribution branch
2022-02-01 22:19:35 +00:00
Actions are run from GitHub repositories, so we check in the packaged action in
the "dist/" directory.
2022-01-31 14:09:42 -05:00
2022-02-01 22:19:35 +00:00
```shell
> npm run build
> git add lib dist
> git commit -a -m "Build and package"
> git push origin releases/v1
2022-01-31 14:09:42 -05:00
```
2022-02-01 22:19:35 +00:00
Now, a release can be created from the branch containing the built action.