GitHub Actions

​

Prerequisites

1. A no-tickets project. Create one in the dashboard.
2. A push token. Generate one from Project settings → Tokens in the dashboard. Treat it like a deploy key.
3. The token stored as a GitHub secret named NT_PUSH_TOKEN on your repo.

​

Minimal workflow

# .github/workflows/notickets.yml
name: no-tickets

on:
  push:
    branches: [main]
  pull_request:

jobs:
  push:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: no-tickets/push-action@v1
        with:
          token: ${{ secrets.NT_PUSH_TOKEN }}

​

What the action does

1. Validates the directory shape (.tiny-brain/<epic>/{epic,feature,fix}.md).
2. Parses every file’s frontmatter and ## Tasks section.
3. Computes the delta against the last push for this branch.
4. Sends the delta with origin: ci and the CI metadata (commit SHA, branch, PR number, run URL).

​

Inputs

​

Outputs

- uses: no-tickets/push-action@v1
  id: push
  with:
    token: ${{ secrets.NT_PUSH_TOKEN }}

- name: Comment on PR
  if: github.event_name == 'pull_request'
  uses: actions/github-script@v7
  with:
    script: |
      github.rest.issues.createComment({
        issue_number: context.issue.number,
        owner: context.repo.owner,
        repo: context.repo.repo,
        body: `📋 [no-tickets board](${{ steps.push.outputs.dashboard-url }}) updated: ${{ steps.push.outputs.delta-summary }}`,
      })

​

Pinning the action version

​

Self-hosted runners

​

Troubleshooting

• 401 Unauthorized — token missing or revoked. Re-issue from the dashboard.
• 403 EntitlementExceeded — your team has hit a hard limit. See Entitlements.
• 422 ValidationError — a frontmatter field is malformed. The error body lists the offending file and field.

​

See also

• Generic CI — same shape using just the CLI
• PR workflows — wire phase transitions to PR state
• Concepts → Push origins