From GitHub issues to searchable fixes: how this wiki works

GitHub issues are excellent records of what one user experienced at one moment, but they are not a troubleshooting handbook. The same failure is reported repeatedly under different titles, useful answers are scattered through comments, and feature requests sit beside actual defects.

CC Switch Wiki turns those records into searchable topic pages without discarding their sources.

Ingest the complete public record

The pipeline synchronizes public issue titles, bodies, labels, states, and comments. Pull requests are marked separately and excluded from issue coverage. Every issue number cited by a page must exist in the local data snapshot.

Separate failures from feature requests

“Please support another provider” and “switching providers erased my configuration” are different kinds of content. The former is a feature request and must not be presented as an existing fix; the latter belongs in troubleshooting.

A one-off report is not forced into a confident topic page. Closed cases with discussion can instead appear in More solved problems as direct links to the original threads.

Cluster on signals that distinguish cases

Clustering considers HTTP status codes, stable error phrases, file paths, environment variables, platforms, clients, and topics. A term that appears in almost every issue inside a cluster is not useful for splitting it.

This groups repeated reports of the same root cause while preventing common background terms such as “local proxy” from merging unrelated failures.

Keep page structure and sources explicit

Each topic follows Symptom / Cause / Fix and lists affected versions, platforms, FAQs, and Source Issues. Error output, logs, commands, code, file paths, and product names stay unchanged for exact search and comparison.

Four gates before publication

1. Schema and immutable-field validation;
2. source auditing for versions, paths, symptoms, and cited issues;
3. one-to-one Chinese and English page validation;
4. full-site checks for internal links, Pagefind, canonical URLs, hreflang, and JSON-LD.

If any gate fails, the page is not deployed. The changelog is also generated directly from pipeline reports, so a model cannot rewrite the underlying numbers.

See About this site for current coverage, counting rules, and the unofficial-community notice.