You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Chore] Harmonize repository metadata and ct-conventions integration with CTBase #313
Agents: read the guide for agents in #310 first (order, difficulty, how to claim an issue, working method). The specification is in this description and in the comments below.
Goal
Harmonize OptimalControlProblems.jl with the conventions of the control-toolbox ecosystem, following the ct-agents harmonization recipes. CTBase.jl is the reference.
the latest ct-conventions release pinned in AGENTS.md and read from a git-ignored clone in .ct-conventions/ (not a git submodule: it breaks Pkg.add on Julia 1.10); AGENTS.md cites rules by identifier; CLAUDE.md redirects to it; CONTRIBUTING.md and _typos.toml updated; every reference to the former Handbook replaced
obsolete workflows removed (AIHello.yml); any other difference with CTBase's workflows reported, not aligned
Progress is tracked in a comment below, ticked when each PR is merged.
Acceptance criteria
AGENTS.md pins a ct-conventions release; no git submodule in the tree; Julia 1.10 installs the package.
No reference to the former Handbook outside CHANGELOG.md and BREAKING.md.
https://github.com/control-toolbox/OptimalControlProblems.jl/issues/new/choose offers the organization's five templates.
The labels the templates and the workflows use exist.
Package-specific workflows and documentation still work.
Notes for this package
Survey of 2026-11-04 against CTFlows.jl, OptimalControl.jl and CTModels.jl:
No AGENTS.md nor CLAUDE.md, although CONTRIBUTING.md (and the README generated from it) refers to AGENTS.md; nothing about .ct-conventions/, .ct-agents/ and .reports/ in .gitignore (theme 1; replaces [Dev] Add AGENTS.md (referenced by CONTRIBUTING.md) #309).
Own .github/ISSUE_TEMPLATE/ (six files) (theme 3).
Labels are GitHub's defaults plus a few (roadmap, paper, internal dev…) (theme 2).
No .JuliaFormatter.toml, no _typos.toml (the spell check passes its identifiers inline in SpellCheck.yml) (theme 4).
Label plan (theme 2): keep these package-specific labels, introduced by #304 (scope modifiers, they trigger nothing on their own): test JuMP backend, test OptimalControl backend, test OptimalControlScalarized backend, test Corleone backend, test comparison. Also keep roadmap and paper (used by #310 and the benchmark-paper themes).
Theme 2 — labels plan (requires maintainer validation before applying).
Surveyed the repository labels and their use in issues/PRs, per the labels recipe. Proposed changes:
Action
Label
Target
Issues affected
Reason
create
—
0
reference set; replaces the package's name
create
—
0
reference set; replaces
create
—
0
reference set; organization template
create
—
0
reference workflow label
create
—
0
reference workflow label
create
—
0
reference workflow label
rename
39
reference name; preserve issue labels
rename
9
reference name; preserve issue labels
keep
—
0
reference label; workflow/bot use
keep
—
4
reference label
keep
—
0
reference label/dependabot
keep
—
15
reference label
keep
—
0
reference label
keep
—
0
reference label
keep
—
1
reference label
keep
—
0
reference label
keep
—
0
reference workflow label
keep
—
0
reference label
keep
—
0
reference label
keep
—
6
package-specific benchmark-paper label, required by #310
obsolete package-specific label; no issues currently carry it
propose delete
—
0
obsolete default label; no issues currently carry it
The plan deliberately does not apply any setting change yet. Please validate the rows above (or state corrections); after validation I will apply only the approved changes and report the final label set.
obsolete package-specific label; no issues currently carry it
propose delete
invalid
—
0
obsolete default label; no issues currently carry it
The plan deliberately does not apply any setting change yet. Please validate the rows above (or state corrections); after validation I will apply only the approved changes and report the final label set.
Correction: the preceding label-plan comment (comment 6629663120) was malformed by shell interpolation of Markdown backticks. Comment 6629666925 is the authoritative, correctly rendered plan; no label settings have been changed.
The approved label plan is applied (comment 6629736595). The work is now split according to the recipe: theme 1 in draft PR #315, themes 4–5 in draft PR #316, and theme 3 in draft PR #317. Theme 3 can be merged after review; its post-merge organization-template check remains to be recorded.
The three pull requests are merged. The repository community profile now points to the organization-wide PR template and code of conduct. This tracking issue can be closed by the maintainer.
Activity
ocots commentedon Nov 4, 2026
Label plan (theme 2): keep these package-specific labels, introduced by #304 (scope modifiers, they trigger nothing on their own):
test JuMP backend,test OptimalControl backend,test OptimalControlScalarized backend,test Corleone backend,test comparison. Also keeproadmapandpaper(used by #310 and the benchmark-paper themes).ocots commentedon Nov 4, 2026
Label plan (theme 2), addition: keep the labels used by the crons of #305:
cron-failure,cron-drafts,cron-capabilities.ocots commentedon Nov 4, 2026
Label plan (theme 2), addition: keep
cron-bugandflaky, used by the per-problem bug issues of #305.ocots commentedon Nov 4, 2026
Label plan (theme 2), correction: the scope label for the fourth modeling is
test ModelingToolkit backend(nottest Corleone backend), see #308.ocots commentedon Nov 4, 2026
Taken by an agent; draft PR to follow.
ocots commentedon Nov 4, 2026
Theme 2 — labels plan (requires maintainer validation before applying).
Surveyed the repository labels and their use in issues/PRs, per the labels recipe. Proposed changes:
The plan deliberately does not apply any setting change yet. Please validate the rows above (or state corrections); after validation I will apply only the approved changes and report the final label set.
ocots commentedon Nov 4, 2026
Theme 2 — labels plan (requires maintainer validation before applying).
Surveyed the repository labels and their use in issues/PRs, per the labels recipe. Proposed changes:
devinternal devnamefeatureenhancementreleaserun breakagerun ci github-runnerrun documentationinternal devdevenhancementfeatureautomated prbugdependenciesdocumentationduplicateformattinggood first issuehelp wantedno changelogquestionwontfixpaperroadmaptest JuMP backendtest OptimalControl backendtest OptimalControlScalarized backendtest ModelingToolkit backendtest comparisoncron-failurecron-draftscron-capabilitiescron-bugflakyhelp sedinvalidThe plan deliberately does not apply any setting change yet. Please validate the rows above (or state corrections); after validation I will apply only the approved changes and report the final label set.
ocots commentedon Nov 4, 2026
Correction: the preceding label-plan comment (comment 6629663120) was malformed by shell interpolation of Markdown backticks. Comment 6629666925 is the authoritative, correctly rendered plan; no label settings have been changed.
ocots commentedon Nov 4, 2026
Theme 2 — labels applied.
The validated plan was applied:
internal dev→dev(39 existing issues preserved)enhancement→feature(9 existing issues preserved)release,run breakage,run ci github-runner, andrun documentation, with CTBase metadata.help sedandinvalid; neither was attached to an issue.paper,roadmap, and the existing package/workflow labels.The final repository label set was checked against the approved plan and the CTBase reference set. No unapproved label was changed.
ocots commentedon Nov 4, 2026
The approved label plan is applied (comment 6629736595). The work is now split according to the recipe: theme 1 in draft PR #315, themes 4–5 in draft PR #316, and theme 3 in draft PR #317. Theme 3 can be merged after review; its post-merge organization-template check remains to be recorded.
ocots commentedon Nov 4, 2026
Harmonization complete.
All five themes are done:
The three pull requests are merged. The repository community profile now points to the organization-wide PR template and code of conduct. This tracking issue can be closed by the maintainer.