Skip to content

fix(scripts): migrar kanban al proyecto #6 y audit sin releases - #41290

Closed
jaminsmoke wants to merge 5 commits into
anomalyco:devfrom
jaminsmoke:kanban-project6
Closed

fix(scripts): migrar kanban al proyecto #6 y audit sin releases#41290
jaminsmoke wants to merge 5 commits into
anomalyco:devfrom
jaminsmoke:kanban-project6

Conversation

@jaminsmoke

Copy link
Copy Markdown

Summary

Contexto

Tras el refork a sst/opencode, el kanban de Jarvis pasó al proyecto #6. Los scripts y el changelog apuntaban aún al proyecto viejo (#5) o fallaban porque el repo nuevo no tiene releases.

Verificación

  • python scripts/kanban-sync.py audit -> OK All items OK! (objetivo v0.1.0, repo sin releases)
  • python -m unittest discover -s scripts/tests -> 34 tests OK
  • python scripts/kanban-sync.py changelog -> regenera HTML + JSON (2 highlights, v0.1.0)

This is a one-time migration commit that overlays the complete Jarvis
working tree (branding, connectors, CI workflows, kanban scripts, tests,
documentation, and all customizations) onto a real fork of sst/opencode.
After this commit, Jarvis shares git history with upstream and can
cherry-pick / merge from OpenCode normally.
Updated all ProjectV2 field IDs, option IDs, and label IDs for the
new jaminsmoke/Jarvis fork. Status field replaced with Estado (custom
field with Detectado/Debate/Roadmap/Ejecutando/Verificando/Changelog
options) since GitHub built-in Status doesn't support custom options.
Deleted the custom Estado field and reverted kanban-sync.py to use the
built-in GitHub Status field (PVTSSF_lAHOBM87Yc4Bfu74zhZ_v1g).
Status options (Detectado/Debate/...) must be added via the GitHub UI.
- kanban-sync.py: corregir REPO_ID transpuesto (R_kgDOTx4wIw) y tratar
repo sin releases como objetivo v0.1.0 en vez de fallar
- generate-changelog-json.py: apuntar a Project #6 con field/option IDs
del kanban nuevo (HighLighted PVTSSF_...wbs, Yes 573cc802)
- docs/changelog: regenerar contra el kanban #6 (v0.1.0, issues 1-2)
@github-actionsgithub-actionsBot added the needs:compliance This means the issue will auto-close after 2 hours. label Aug 8, 2026
@github-actions

Copy link
Copy Markdown
Contributor

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@jaminsmoke

Copy link
Copy Markdown
Author

Creado por error: el PR pertenece a jaminsmoke/Jarvis, no al upstream.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs:complianceThis means the issue will auto-close after 2 hours.needs:issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@jaminsmoke