[PR #105] [MERGED] docs: fix stale references to the removed GitHub-export button #104

New issue

Closed

opened 2026-08-16 07:30:52 +02:00 by zaph0d · 0 comments

zaph0d commented

2026-08-16 07:30:52 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/niels-emmer/myace/pull/105
Author: @niels-emmer
Created: 8/15/2026
Status: ✅ Merged
Merged: 8/15/2026
Merged by: @niels-emmer

Base: main ← Head: docs/audit-post-104

📝 Commits (1)

b105c52 docs: fix stale references to the removed GitHub-export button

📊 Changes

4 files changed (+20 additions, -13 deletions)

View changed files

📝 AGENTS.md (+10 -6)
📝 README.md (+0 -2)
📝 SECURITY.md (+4 -2)
📝 docs/plan-collection-actions.md (+6 -3)

📄 Description

Summary

Post-#104 doc audit. The frontend "Export to GitHub" button on CollectionDetail.tsx was removed in #104 (publishing now goes exclusively through "Publish to Community"), but several docs still described it as a live, UI-surfaced feature. The backend endpoint (POST /collections/{id}/export/github) and github_export.py service are untouched — only docs needed fixing.

README.md — dropped the "Export back out" bullet from the Features list (no longer an accurate product feature description)
AGENTS.md rule 28 — replaced the stale "two things called export" bullet with one noting the button is gone and the endpoint is now direct-API-only
docs/plan-collection-actions.md — noted the second supersession in the status banner
SECURITY.md — reworded the token-handling note to describe the API endpoint rather than a UI "feature"

No functional/code changes — docs only.

Test plan

Grepped repo-wide for remaining "Export to GitHub" references — the two left are correctly historical/clarifying
No code files touched (git diff --stat confirms doc-only diff)

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/niels-emmer/myace/pull/105 **Author:** [@niels-emmer](https://github.com/niels-emmer) **Created:** 8/15/2026 **Status:** ✅ Merged **Merged:** 8/15/2026 **Merged by:** [@niels-emmer](https://github.com/niels-emmer) **Base:** `main` ← **Head:** `docs/audit-post-104` --- ### 📝 Commits (1) - [`b105c52`](https://github.com/niels-emmer/myace/commit/b105c52ca94a1f60e4df4d5bf321b21ae900d251) docs: fix stale references to the removed GitHub-export button ### 📊 Changes **4 files changed** (+20 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `AGENTS.md` (+10 -6) 📝 `README.md` (+0 -2) 📝 `SECURITY.md` (+4 -2) 📝 `docs/plan-collection-actions.md` (+6 -3) </details> ### 📄 Description ## Summary Post-#104 doc audit. The frontend "Export to GitHub" button on `CollectionDetail.tsx` was removed in #104 (publishing now goes exclusively through "Publish to Community"), but several docs still described it as a live, UI-surfaced feature. The backend endpoint (`POST /collections/{id}/export/github`) and `github_export.py` service are untouched — only docs needed fixing. - `README.md` — dropped the "Export back out" bullet from the Features list (no longer an accurate product feature description) - `AGENTS.md` rule 28 — replaced the stale "two things called export" bullet with one noting the button is gone and the endpoint is now direct-API-only - `docs/plan-collection-actions.md` — noted the second supersession in the status banner - `SECURITY.md` — reworded the token-handling note to describe the API endpoint rather than a UI "feature" No functional/code changes — docs only. ## Test plan - [x] Grepped repo-wide for remaining "Export to GitHub" references — the two left are correctly historical/clarifying - [x] No code files touched (`git diff --stat` confirms doc-only diff) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

zaph0d

2026-08-16 07:30:52 +02:00