issue-ops/IssueOps Demo Reservation Action
Process reservation requests for a fictional business
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| action | The action to take (`init`, `reserve`, `cancel`, or `expire`). | yes | — |
| github_token | The GitHub token to use for interacting with the GitHub API. | yes | ${{ github.token }} |
| issue_body | The issue body as a JSON string. This is typically the output of the `issue-ops/parser` action. | no | — |
| issue_template_path | Path to the issue template file from the root of the repository (e.g. `.github/ISSUE_TEMPLATE/reservation.yml`). | yes | — |
| project_number | The number of the project board where reservations are managed. | yes | — |
| workspace | The path where the repository has been cloned using the `actions/checkout` step. This is required to find the issue form template file. | yes | ${{ github.workspace }} |
Outputs
| name | description |
|---|---|
| json | The parsed issue as a JSON string |