bcgov/Gherking extractor for GitHub Issues
GitHub Action that processes Gherkin content from issues and turn them into a content that can be then saved into a file
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Feb 25, 2026
- License
- Apache 2.0
Pinned Snippet
uses: bcgov/action-gherkin-issue-processor@996c4dd154e93e49a3ddeead7c26c18c3a1602f3 # v1.1.3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| issue | The issue number | yes | — |
| default_title | A default title for the issue, to check if the user has changed it | — | — |
| update_title | Defines if the issue title should be updated in case it is not different from the default one | — | false |
| token | Your GitHub token or a personal access token | — | ${{ github.token }} |
| owner | The owner of the repository | — | ${{ github.repository_owner }} |
| repo | The repository name | — | ${{ github.repository }} |
Outputs
| name | description |
|---|---|
| title | The title of the issue. Usually the original title, unless it was updated |
| sanitized_title | The title of the issue in a clean and sanitized format that can be used as a file name |
| body | The original body of the issue |
| feature | The feature content |