Skip to content
.github/workflows/respond-to-triaged-issue-comment-local.yml

When will the official version be available? #3

Sign in to view logs

When will the official version be available?

When will the official version be available? #3

Workflow file for this run

.github/workflows/respond-to-triaged-issue-comment-local.yml at fc1d2ff
name: Respond to Triaged Issue Comment (Local)
on:
issue_comment:
types: [created]
concurrency:
group: respond-to-triaged-issue-comment-${{ github.event.comment.id || github.run_id }}
cancel-in-progress: false
jobs:
# Mention, bot, event-type, and trust gates all live in the reusable
# workflow (``respond-to-triaged-issue-comment.yml``). This adapter
# exists only to subscribe to the GitHub event that can carry an
# ``@oz-agent`` mention on a triaged issue and delegate it through
# ``workflow_call``.
respond_inline:
permissions:
contents: read
issues: write
uses: warpdotdev/oz-for-oss/.github/workflows/respond-to-triaged-issue-comment.yml@main

Check failure on line 18 in .github/workflows/respond-to-triaged-issue-comment-local.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/respond-to-triaged-issue-comment-local.yml

Invalid workflow file 

error parsing called workflow
".github/workflows/respond-to-triaged-issue-comment-local.yml"
-> "warpdotdev/oz-for-oss/.github/workflows/respond-to-triaged-issue-comment.yml@main"
: failed to fetch workflow: workflow was not found.
secrets:
OZ_MGMT_GHA_APP_ID: ${{ secrets.OZ_MGMT_GHA_APP_ID }}
OZ_MGMT_GHA_PRIVATE_KEY: ${{ secrets.OZ_MGMT_GHA_PRIVATE_KEY }}
OSS_WARP_API_KEY: ${{ secrets.OSS_WARP_API_KEY }}