Skip to content

Remove Boost Dev Workflow Bottleneck #74

@iTinkerBell

Description

@iTinkerBell
  • Identify workflow bottlenecks: systematically find what slows down the workflow and remove/reduce those obstacles.
  • Faster CI feedback: avoid the current “push branch → wait ~45 minutes” loop; shorten turnaround materially.
  • Stop editing ci.yml: CI should not require manual maintenance of complex GitHub Actions YAML.
  • Single-file build/CI spec: allow a simple per-library metadata file (example name given: AGENT.md) stating:
    • compiler minimums (e.g., gcc 7+, clang 13+, msvc 14.3+)
    • required C++ standard (e.g., C++20+)
    • docs pipeline note (e.g., “Docs are built with antora”)
  • Reduce/avoid CMakeLists.txt maintenance: lower the ongoing burden of build system upkeep.
  • Make repos easier for LLMs to help: adjust project structure/conventions so AI tools can operate more effectively.
  • Open Boost superproject in Cursor: enable a workflow where the entire Boost superproject can be used in Cursor effectively (implies scalability/performance of tooling + indexing).

Sub-issues

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions