Skip to content

docs(#4886): label deprecated features in user documentation#5462

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/4886-label-deprecated-docs
Open

docs(#4886): label deprecated features in user documentation#5462
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/4886-label-deprecated-docs

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

Add visible deprecation notices and migration guidance to user-facing documentation for deprecated features (runner_env, customized/ overlay, per-org mode, admin install), establish a contributor convention for deprecation labeling, and document a documentation versioning feasibility investigation.

Related Issue

Closes #4886

Changes

  • Deprecation convention (CONTRIBUTING.md): Add a "Deprecation notices in documentation" section with three templates (blockquote, inline, index entry) and guidance on what to include and when to add notices
  • runner_env labeling (bring-your-own-agent.md): Add deprecation notice with migration guidance to env.runner per ADR-0055; mark in field reference table and code examples
  • Per-org mode (org-mode.md): Update "Planned deprecation" to "Deprecated" with migration command per ADR-0044; mark in guides/README.md index
  • customized/ overlay (customizing-agents.md): Convert inline deprecation annotations to proper blockquote notices linking ADR-0064 for customized/skills/ and customized/agents/ sections
  • admin install (cli-internals.md): Add ADR-0069 link and use consistent deprecation format
  • ADR link (customizing-with-agents-md.md): Add missing hyperlink to ADR-0064
  • Versioning investigation (doc-site.md): Evaluate four approaches (VitePress multi-version, branch-based, git tag snapshots, deprecation-only) with recommendation to revisit when features are removed

Testing

  • lychee markdown link checker passes on all changed files (0 errors)
  • scan-secrets passes on all changed files
  • gitlint passes on commit message
  • No Go code changed — docs-only PR

Checklist

  • PR title follows Conventional Commits (correct type, ! for breaking changes)
  • Commits are signed off (DCO) — human and human-directed agent sessions only
  • I wrote this contribution myself and can explain all changes in it

Closes #4886

Post-script verification

  • Branch is not main/master (agent/4886-label-deprecated-docs)
  • Secret scan passed (gitleaks — cb2bcd9f282952232249eca4a281a3392a617d41..HEAD)
  • PR body secret scan passed (gitleaks — no-git)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Add visible deprecation notices to user-facing documentation for
deprecated features, establish a contributor convention for
deprecation labeling, and document a versioning investigation.

Changes:
- Add deprecation notice convention to CONTRIBUTING.md with
  blockquote, inline, and index entry templates
- Label `runner_env` as deprecated in bring-your-own-agent.md
  with migration guidance to `env.runner` (ADR 0055)
- Update per-org mode notice from "Planned deprecation" to
  "Deprecated" with migration guidance (ADR 0044)
- Convert inline deprecation annotations to blockquote notices
  in customizing-agents.md for `customized/skills/` and
  `customized/agents/` sections (ADR 0064)
- Add ADR link to `admin install` deprecation in cli-internals.md
- Add ADR link to `customized/` deprecation reference in
  customizing-with-agents-md.md
- Mark org-mode as deprecated in guides/README.md index
- Add documentation versioning investigation to doc-site.md
  evaluating four approaches with recommendation

Note: pre-commit could not run (network restriction in sandbox).
The post-script runs an authoritative pre-commit check.

Closes #4886
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner July 22, 2026 13:43
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Agent PR ready for human review label Jul 22, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Jul 22, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 1:45 PM UTC · Completed 2:01 PM UTC
Commit: 3db5677 · View workflow run →

@github-actions

Copy link
Copy Markdown

Site preview

Preview: https://7da21084-site.fullsend-ai.workers.dev

Commit: 3db5677f8b0096e2546400f9723b9046adcccd4f

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium

  • [documentation-accuracy] docs/guides/dev/cli-internals.md:185 — The deprecation notice attributes the admin install deprecation to ADR-0069 ("Ready-made configuration presets for simplified installation"), but ADR-0069 does not make the deprecation decision — it merely mentions the deprecation as pre-existing context in its Context section. The actual deprecation of per-org commands including admin install <org> is decided in ADR-0044 ("Deprecate per-org installation mode"). Readers following the ADR-0069 link will find a decision about config presets and layered configuration, not about admin install deprecation.
    Remediation: Change the ADR reference to ADR-0044, or omit the ADR reference and state the deprecation without attribution.

Low

  • [migration-guidance] docs/guides/getting-started/org-mode.md:12 — The new migration guidance says "run fullsend github setup per-repo instead of fullsend admin install per-org." However, ADR-0044 Section 3 prescribes a more detailed migration process using fullsend admin install <owner>/<repo> with specific flags or fullsend admin migrate <org> <repo>. The simplified guidance risks users missing critical migration steps.
    Remediation: Link to the full migration plan in ADR-0044 Section 3, or mention fullsend admin migrate which is the purpose-built migration command.

  • [stale-doc] docs/architecture.md — The "Configuration layering" section describes the customized/ overlay mechanism. It mentions deprecation inline but not in the blockquote format established by this PR's new CONTRIBUTING.md convention.
    Remediation: Add a blockquote deprecation notice referencing ADR-0064 to match the new convention.

  • [stale-doc] docs/guides/user/running-agents-locally.md — The "Simulating Fullsend's real customization layers" section provides instructions for using the customized/ overlay without a deprecation notice.
    Remediation: Add a deprecation notice referencing ADR-0064 and pointing to config-driven agent registration.


Labels: PR is documentation-only work establishing deprecation conventions and labeling deprecated features across user-facing guides

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

The typical handoff: a GCP admin runs `mint deploy`, `mint enroll`, and `inference provision`, then passes the mint URL and WIF provider resource name to a GitHub maintainer who runs `github setup --mint-url=... --inference-wif-provider=...`. See [Advanced setup](../infrastructure/advanced-setup.md).

> **Note:** The legacy `admin install` command wraps all phases into a single invocation but is deprecated. The standalone commands above are the recommended path. See the [Unified Installation Flow](#unified-installation-flow) section below for how the phases are structured internally.
> **Deprecated:** The `admin install` command is deprecated per

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[medium] documentation-accuracy

The deprecation notice attributes the admin install deprecation to ADR-0069 ('Ready-made configuration presets'), but ADR-0069 does not make the deprecation decision — it merely mentions the deprecation as pre-existing context. The actual deprecation of per-org commands including admin install is decided in ADR-0044 ('Deprecate per-org installation mode'). Readers following the ADR-0069 link will find a decision about config presets, not about admin install deprecation.

Suggested fix: Change the ADR reference to ADR-0044, or omit the ADR reference and state the deprecation without attribution.

> New installations should use the [per-repo Getting Started guides](README.md).
> Existing per-org installations continue to work and are fully supported during
> the transition. To migrate, run `fullsend github setup` per-repo instead of
> `fullsend admin install` per-org.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] migration-guidance

The migration guidance says 'run fullsend github setup per-repo instead of fullsend admin install per-org.' ADR-0044 Section 3 prescribes a more detailed migration process using fullsend admin install / with specific flags or fullsend admin migrate . The simplified guidance risks users missing critical migration steps.

Suggested fix: Link to the full migration plan in ADR-0044 Section 3, or mention fullsend admin migrate.

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment documentation type/chore Maintenance and housekeeping tasks labels Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation ready-for-review Agent PR ready for human review requires-manual-review Review requires human judgment type/chore Maintenance and housekeeping tasks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clearly label deprecated features in user documentation

1 participant