Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
15 lines
553 B
Plaintext
15 lines
553 B
Plaintext
You can configure some aspects of the GitHub Actions-based CI on a
|
|
per-repository basis by setting "variables" and "secrets" from with the
|
|
GitHub web interface. These can be found at:
|
|
|
|
https://github.com/<user>/git/settings/secrets/actions
|
|
|
|
The following variables can be used:
|
|
|
|
- CI_BRANCHES
|
|
|
|
By default, CI is run when any branch is pushed. If this variable is
|
|
non-empty, then only the branches it lists will run CI. Branch names
|
|
should be separated by spaces, and should use their shortened form
|
|
(e.g., "main", not "refs/heads/main").
|