Skip to content

feat(workflows): add reusable promotion runtimes - #60

Merged
0xPlayerOne merged 1 commit into
stagingfrom
feat/reusable-promotion-workflows
Jul 28, 2026
Merged

0xPlayerOne merged 1 commit into
stagingfrom
feat/reusable-promotion-workflows

Conversation

@0xPlayerOne

Copy link
Copy Markdown
Owner

Summary

  • add versioned reusable Draft PR and Release PR runtimes
  • preserve existing local callers during the bootstrap release
  • document the two-phase runtime migration

Validation

  • node --check src/cli.mjs
  • bash -n sync-template.sh
  • workflow YAML parse
  • npm test
  • npm run pack:check

@0xPlayerOne
0xPlayerOne force-pushed the feat/reusable-promotion-workflows branch from 6d8d754 to e97a762 Compare July 28, 2026 08:43
@0xPlayerOne
0xPlayerOne merged commit f9334e3 into staging Jul 28, 2026
15 checks passed
@0xPlayerOne
0xPlayerOne deleted the feat/reusable-promotion-workflows branch July 28, 2026 08:43

**CI Status:** Pending — this workflow triggered on push to \`$BRANCH\`."

- name: Mark ready

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: Draft PR immediately marked as ready for review

The workflow creates a draft PR (line 36: --draft) but the subsequent "Mark ready" step (line 50) calls gh pr ready to remove the draft status. This is contradictory: a draft PR signals that it is not yet ready for review, but the step immediately marks it as ready, defeating the purpose of the draft status.


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

TOTAL_COMMITS=$(jq -r '.total_commits // 0' "$COMPARE_FILE")
if [ "$TOTAL_COMMITS" -gt 100 ]; then
LAST_PAGE=$(( (TOTAL_COMMITS + 99) / 100 ))
gh api "$COMPARE_URL?per_page=100&page=$LAST_PAGE" > "$COMPARE_FILE"

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: Pagination fetches oldest commits instead of newest when >100 commits exist

When the compare API returns more than 100 commits, the code fetches the last page (page=$LAST_PAGE), which contains the oldest commits. The first page (fetched on line 42) already contains the newest commits, but it gets overwritten. The release PR body will then list the oldest commits rather than the most recent ones.


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

@kilo-code-bot

kilo-code-bot Bot commented Jul 28, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: 2 Issues Found | Recommendation: Address before merge

Overview

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

WARNING

File Line Issue
.github/workflows/reusable-draft-pr.yml 44 Draft PR immediately marked as ready for review — the "Mark ready" step calls gh pr ready after creating the PR with --draft, which is contradictory
.github/workflows/reusable-release-pr.yml 46 Pagination fetches the last page (oldest commits) instead of the first page (newest commits) when >100 commits exist between main and staging
Files Reviewed (4 files)
  • .github/scripts/sync-template.sh - 0 issues
  • .github/workflows/reusable-draft-pr.yml - 1 issue
  • .github/workflows/reusable-release-pr.yml - 1 issue
  • README.md - 0 issues

Fix these issues in Kilo Cloud


Reviewed by ling-3.0-flash-free · Input: 254K · Output: 25.4K · Cached: 687K

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