Per repo install still creates .fullsend repo

[deboer-tim]

I'm testing the per-repo install for teams that share an org, but the .fullsend repo was still automatically created using my account.

[fullsend-ai-triage]

Triage Summary

Based on the full comment thread, this issue has been clarified: the per-repo installer itself works correctly. The root problem is that the install documentation structure leads shared-org users down the org-level install path before they ever see the per-repo option.

What happened

You followed the install guide top-down and ran the org-level command (fullsend admin install ORG_NAME) as directed in step 1. This created the .fullsend config repo — which is expected for org-wide installs but unwanted for independent per-repo setups. The per-repo format (fullsend admin install ORG/REPO) works correctly, as you confirmed.

Recommended fix

Restructure the install docs to present a clear org-wide vs. per-repo decision point before any install commands. Per-repo install should be a first-class path, not a subsection after org-level steps. PR #1483 (simplified install guide) is already in flight and is the right place to address this.

Proposed verification

Manual review: A new user targeting a shared-org scenario should be able
to identify and follow the per-repo install path from the guide without
first executing any org-level commands.

Re-categorizing this from bug to documentation since the installer behavior is working as designed — it's the docs that need restructuring.

---

Labels: Reclassifying as documentation since the installer works correctly and the root cause is doc structure; removing type/bug accordingly.

Previous run

Thanks for sharing the exact command — that confirms you ran the org-level installer (fullsend admin install "$ORG_NAME"), which creates the .fullsend config repo by design.

The per-repo format is fullsend admin install ORG/REPO. This is the key open question that will determine next steps:

Have you tried running fullsend admin install ORG_NAME/REPO_NAME (with a slash)? If that command also creates a .fullsend repo, that would be a bug worth fixing here. If it doesn't, then the behavior you experienced is expected for the org-level path, and your multi-team shared-org use case would be tracked under #727 (independent per-repo installer).

Please give the per-repo format a try and let us know the result — that single data point will resolve whether this is a defect or a feature gap.

Previous run (2)

Thanks for sharing the exact command — that's very helpful.

The command you ran (fullsend admin install "$ORG_NAME") is the org-level installer, which creates the .fullsend config repo by design. The per-repo format is fullsend admin install ORG/REPO (with a slash between org and repo name).

The distinction matters because the independent per-repo installer (#727) is still in progress. Your use case — multiple independent teams sharing an org — is exactly what #727 aims to support, but several of its acceptance criteria haven't been checked off yet.

Could you try running the per-repo format (fullsend admin install ORG/REPO) and let us know whether it also creates the .fullsend repo? That would tell us whether this is a bug in the per-repo code path or whether the feature you need is the one tracked in #727.

Previous run (3)

Thanks for the additional context about the multi-team shared-org use case — that's a meaningful distinction from single-repo-at-a-time onboarding.

To move forward, we still need the exact command you ran and its terminal output. Specifically:

• Did you run fullsend admin install ORG/REPO (the per-repo format), or fullsend admin install and then select a single repo interactively?

This distinction is critical because the fully independent per-repo installer (#727) is still in progress — several of its acceptance criteria (including "does not depend on any org-level configuration") are not yet checked off. If you used the org-level install path targeting one repo, the .fullsend repo creation may be expected current behavior rather than a bug. The exact command and output will let us determine which install code path ran and whether this is a defect or a not-yet-implemented feature gap.

Previous run (4)

Thanks for clarifying the multi-team use case — that distinction between "one repo at a time" and "independent teams in a shared org" is helpful.

To move forward, we still need the exact command you ran (e.g., fullsend admin install --repo <repo> vs. fullsend admin install with a single repo selected) and its terminal output. This matters because the fully independent per-repo installer is tracked in #727 and its acceptance criteria — including "does not depend on any org-level configuration" — are not yet checked off. Knowing which install path you used will help us determine whether this is a bug in the current code or expected behavior from a feature that hasn't fully landed yet.

---

Labels: Issue already has correct component/install and type/bug labels; adding priority/medium given it affects multi-team org scenarios.

Previous run (5)

Thanks for the report. To diagnose this, could you share the exact fullsend install command you ran (redacting any sensitive org/repo names) and its full terminal output? Specifically, we need to understand whether the .fullsend repo was freshly created by this invocation or whether it already existed in the org from a prior org-wide install — the per-repo install path in the code does not call the config-repo creation function, so the distinction matters.

---

Labels: This issue involves per-repo installation behavior and the .fullsend config repo, touching the install component and scaffold area.

[deboer-tim]

To be clear there is 'I only want to onboard one repo at a time' vs 'I'm one of three teams/repos in the org and I'm the only one using fullsend' (or others are using fullsend too, but independently). The .fullsend repo would be fine in the first case, but I thought the current installer was starting to support the second, where it clearly wouldn't be.

[rh-hemartin]

Which command did you use, the format for repo install is fullsend admin install ORG/REPO, even then it is creating the .fullsend repository?

[deboer-tim]

This was during step 1 of the installer 1. Run the installer (which hasn't finished successfully yet), I haven't even gotten to the multi-org or per-repo section:

fullsend admin install "$ORG_NAME" \
  --inference-project "$GCP_PROJECT" \
  --mint-project "$GCP_PROJECT"