zeekay
f4e005afb9
The forge takes a repo's workflows from the first of its search paths that exists, and .hanzo/workflows comes before .github/workflows. This repo has carried .hanzo/workflows/cicd.yml since it adopted the canonical lane, so everything under .github/workflows has been inert since that day. The run history says the same: of eight runs, four are the live cicd lane and the other four — linting, licenses and two stale-pr-closer — were all cancelled, queued against ubuntu-latest and debian-12, labels no runner here answers. So this deletes dead files rather than migrating live ones, and nothing is revived: - check-pr-body, labeler, stale-pr-closer and dependabot-pnpm-dedupe are GitHub-platform automation: a dependabot body rewrite, a pull request labeller, a stale closer, and a lockfile dedupe on branches that do not exist here. - linting, licenses, migration-tests and tests hold the real value, and all four want the same harness — a discourse_test container, a bundle install of the whole Gemfile, a pnpm install of a monorepo this size, and for the suites a Postgres and a Redis. hanzo.yml already records why that is a harness rather than a push gate, and this repo's gate stays what it says it is: every tracked Ruby file parses. - release-notes turned bin/rake release_note:generate into a step summary and an artifact. The rake task is untouched and still runs by hand. What goes with them, none of which has run since the lane moved: rubocop, syntax_tree, eslint, prettier, ember template lint, stylelint, glint, the i18n lint, the RubyGems and JS licence checks, and the rspec, qunit and migration suites.
hanzoai/forum
A tracking fork of Discourse, kept for a future Hanzo community forum.
Status
Nothing Hanzo-specific has been built on top of it yet, and nothing is deployed. The commits on this fork are CI, branding assets and agent docs; the application code is upstream's. If you are looking for a running Hanzo forum, there isn't one — start at docs.hanzo.ai, or open an issue on the repository you have a question about under github.com/hanzoai.
If you want to run Discourse, or you have a Discourse question, go to discourse.org and meta.discourse.org. They maintain it; we only track it.
Working on this fork
The upstream setup guides apply unchanged — Ruby 3.2+, PostgreSQL 13, Redis 7:
Production install: docs/INSTALL.md.
Changes that belong upstream should go upstream — send them to discourse/discourse rather than here, so this fork stays easy to rebase.
Lineage and license
Discourse, copyright 2014–2025 Civilized Discourse Construction Kit, Inc., licensed GPL-2.0-or-later. This fork keeps that licence; see LICENSE. The Discourse logo and "Discourse Forum" are their trademarks, and this fork is not affiliated with or endorsed by them.