Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[bug] codebase --deep-enrich in a team repo reports success but never publishes, and leaves the team clone dirty

Closed
  • Is something wrong?
#1,537 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Kiddo4993 is already working on this.

Since Oct 28, 2026.

  • #1538 by @Kiddo4993 — open

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
cli, devtools

Research direction

Compare the team repo publishing path used by teamai import with codebase --deep-enrich when --output is omitted; the issue identifies the missing publish step and provides a local bare repo reproduction. Trace both command entry points and their publish logic, then reproduce the dirty clone and verify that success leaves no generated files uncommitted. Pull request #1538 is already open.

Written by the indexing model from the issue text.

Description

bug help wanted

What happens

In a team that keeps its knowledge in the team repo (no --output), teamai codebase --deep-enrich --project <name> writes the generated docs into the local team clone and stops there. It reports success, but nothing reaches the remote, and the clone is left dirty:

$ teamai import --dir ./svc                     # deep enrich incomplete on the first try
$ teamai codebase --deep-enrich --project svc
✔ deep-enrich[svc]: Deep knowledge generation complete
Deep enrichment complete: project=svc           exit 0
$ git -C <team clone> status --short
 M teamwiki/evidence/code/svc/_review/progress.json
 M teamwiki/router.md
?? teamwiki/evidence/code/svc/docs/architecture.md
?? teamwiki/evidence/code/svc/docs/lib.md
# the remote still has no architecture.md or lib.md
$ teamai push
✖ Cannot push: the team repo has uncommitted changes. Commit or stash them first. Paths: teamwiki/router.md

teamai pull exits 0 and keeps the files local, so nothing ever publishes them. The member's next teamai push, for example to share a skill, fails until they clean the clone by hand.

Re-running the same import (teamai import --dir ./svc, or --from-repo <url>) resumes deep enrich and publishes the docs.

Why

codebase --deep-enrich writes into the team clone like import does, but unlike import it has no publish step for the team-repo case. With --output, it writes to that directory and there is nothing to publish, so that case works.

Evidence

Built CLI on main (898b82af), isolated HOME, a team from teamai init <team> --provider git on a local bare repo, and a stub AI tool. The run is in the steps above. Found while reviewing #1534, whose retry line for import points at this command.

Possible fix

  • After codebase --deep-enrich writes into the team clone, publish the way import does (same push or branch path), or
  • refuse in a team repo without --output and name the teamai import … command that resumes and publishes.

Either way, the command never leaves the team clone dirty after reporting success.

Dominant language
TypeScript
Stars
5.6k
Forks
471
Avg merge
19h 39m
Merged PRs (30d)
404

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Tencent/teamai-cli

All issues in Tencent/teamai-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.