Skip to content

Track issues on the Operations org board#15

Merged
brettstirlingbond merged 4 commits into
mainfrom
chore/operations-board
Jul 14, 2026
Merged

Track issues on the Operations org board#15
brettstirlingbond merged 4 commits into
mainfrom
chore/operations-board

Conversation

@brettstirlingbond

Copy link
Copy Markdown
Contributor

Adds this repo to the org-level Operations Kanban board (Todo / In Progress / Done) that coordinates Brett's and Devin's work across next-mind, campaigns-os, nextcommerce-site, guides, and docs.

  • .github/workflows/add-to-project.yml — auto-adds opened/reopened issues to the board
  • Board note documenting the claim protocol for agent sessions (assign yourself + move card to In Progress before starting; Closes #<n> in PRs)

Prerequisite: the workflow needs the org Actions secret ADD_TO_PROJECT_PAT (classic PAT with repo + project scopes, shared to this repo). Until it's set, the Action will fail and issues must be added to the board manually.

Companion PR with full conventions + the /next-board skill: NextCommerceCo/next-mind#602

🤖 Generated with Claude Code

Auto-add opened/reopened issues to the org-level Operations Kanban board
(NextCommerceCo project 10) and document the claim protocol for agent
sessions. Requires the org secret ADD_TO_PROJECT_PAT.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 14, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
nextcommerce-docs 90f2621 Commit Preview URL

Branch Preview URL
Jul 14 2026, 10:38 AM

Comment thread .github/workflows/add-to-project.yml Outdated
add-to-project:
runs-on: ubuntu-latest
steps:
- uses: actions/add-to-project@v1.0.2

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Action pinned to a mutable tag (v1.0.2) instead of an immutable commit SHA.

Pin third-party Actions by full SHA to mitigate tag-mutation / supply-chain hijack, per GitHub Hardening Guides. The version tag can be republished or re-pointed by the maintainer, and downstream workflows will pick up the new code on the next re-run without review.

Suggested remediation: pin to the SHA corresponding to v1.0.2 with the tag as a comment, e.g.:

Suggested change
- uses: actions/add-to-project@v1.0.2
- uses: actions/add-to-project@<full-40-char-sha> # v1.0.2

Reply with @kilocode-bot fix it to have Kilo Code address this issue.


jobs:
add-to-project:
runs-on: ubuntu-latest

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: No explicit permissions: block — defaults to the repo's default token scopes.

Best practice for least-privilege workflows is to declare the minimal permissions needed. This job only reads issue metadata; a issues: read grant would suffice and limits blast radius if the PAT or default token is ever compromised.

Suggested change
runs-on: ubuntu-latest
permissions:
issues: read

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

Comment thread AGENTS.md Outdated

Before starting work on an issue: check it is not assigned to someone else,
assign yourself (`gh issue edit <n> --add-assignee @me`), and move the card to
In Progress. Open PRs with `Closes #<n>` so the card moves to Done on merge.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: The statement "the card moves to Done on merge" is not guaranteed by this workflow.

actions/add-to-project@v1 only adds cards (on opened/reopened). It does not move cards to Done when an issue is closed or its linked PR is merged — that requires either the GitHub Projects UI auto-move rules (org-level, not visible here) or a separate workflow (likely in next-mind per the PR description). The phrasing reads as if this repo's automation drives the Done transition, which could mislead agents into assuming a missing card transition is a bug here.

Consider clarifying, e.g.: "Open PRs with Closes #<n> so the card moves to Done via the board's auto-move rules / companion automation."


Reply with @kilocode-bot fix it to have Kilo Code address this issue.

@kilo-code-bot

kilo-code-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The incremental commits (43ba7c890f2621) address the previously reported concerns:

  • AGENTS.md (line 51): Reworded to attribute the Done transition to the board's built-in "Item closed" automation rather than this repo's workflow. Resolves the prior SUGGESTION.
  • .github/workflows/add-to-project.yml (line 17): Added timeout-minutes: 5 to bound the add-to-project step below the default 360-minute ceiling. Defensible hardening; no issue.

The previously unresolved WARNING (mutable-tag action pin) and SUGGESTION (missing permissions: block) are not on lines changed in this incremental update, so they remain in their existing comments for downstream remediation.

Files Reviewed (2 files)
  • .github/workflows/add-to-project.yml
  • AGENTS.md
Previous Review Summaries (2 snapshots, latest commit 43ba7c8)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 43ba7c8)

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 2
Issue Details (click to expand)

WARNING

File Line Issue
.github/workflows/add-to-project.yml 11 actions/add-to-project pinned to mutable tag v1.0.2 instead of an immutable commit SHA — supply-chain risk

SUGGESTION

File Line Issue
.github/workflows/add-to-project.yml 9 No explicit permissions: block; should scope to issues: read for least privilege
AGENTS.md 51 "card moves to Done on merge" is not provided by this workflow (add-to-project@v1 only adds cards; Done transition requires org-level auto-move rules or companion automation)
Files Reviewed (2 files)
  • .github/workflows/add-to-project.yml - 2 issues
  • AGENTS.md - 1 issue

Fix these issues in Kilo Cloud

Previous review (commit 7b62256)

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 2
Issue Details (click to expand)

WARNING

File Line Issue
.github/workflows/add-to-project.yml 11 actions/add-to-project pinned to mutable tag v1.0.2 instead of an immutable commit SHA — supply-chain risk

SUGGESTION

File Line Issue
.github/workflows/add-to-project.yml 9 No explicit permissions: block; should scope to issues: read for least privilege
AGENTS.md 51 "card moves to Done on merge" is not provided by this workflow (add-to-project@v1 only adds cards; Done transition requires org-level auto-move rules or companion automation)
Files Reviewed (2 files)
  • .github/workflows/add-to-project.yml - 2 issues
  • AGENTS.md - 1 issue

Fix these issues in Kilo Cloud


Reviewed by minimax-m3 · Input: 21.8K · Output: 1.8K · Cached: 152.5K

brettstirlingbond and others added 3 commits July 14, 2026 11:47
…er-author gate

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
campaigns-os and docs are public; the board-conventions doc lives in the
private next-mind repo. Point contributors to the /next-board skill instead
of the private path. Fixes the forbidden-private-strings check.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…n board automation

- timeout-minutes: 5 (default 360 is too high for add-to-project)
- reword the Done transition to name the board's built-in 'Item closed'
  workflow rather than implying this repo's workflow drives it

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@brettstirlingbond
brettstirlingbond merged commit 4c794b8 into main Jul 14, 2026
4 checks passed
@brettstirlingbond
brettstirlingbond deleted the chore/operations-board branch July 14, 2026 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant