ThemeGrill

Themes and plugins for WordPress — ColorMag, Zakra, Flash, and 25+ others across this org's repos.

About tg-autopilot

Several of this org's repos receive automated activity from tg-autopilot, a shared machine-user account (not a bot account — its GitHub API type is User) used across ThemeGrill's repos here and in wpeverest. If you see a PR comment with a build download link, a Copilot review request, or an issue labeled bug-report-triage, it came from tg-autopilot, not a person.

What it does in this org's repos:

• PR build-zip comment — on a non-draft PR, builds a plugin/theme zip from the head commit and posts (then keeps updating) one comment with a direct, no-login download link.
• Copilot review on comment — commenting @tg-autopilot review on a PR requests a Copilot code review through tg-autopilot's seat, so reviewers don't each need their own.
• Crisp support triage — customer support conversations in Crisp are periodically read, classified, and (when they describe a genuine bug or feature request) turned into a GitHub issue here automatically, labeled bug-report,bug-report-triage or feature-request,bug-report-triage. Each such issue's body ends with a Source: line linking the originating Crisp conversation and a Confidence: NN/100 self-estimate — read that before assuming the diagnosis is exact; low-confidence issues are filed deliberately rather than silently dropped, but still need a human look.
• A recurrence of an already-filed issue gets a comment noting another user hit the same thing, not a duplicate issue.

The actual workflows, scripts, and setup docs all live in wpeverest/.github — that's the shared automation home for both orgs, kept in one place regardless of which org's repos it targets. Start there if you want to see how any of this works, change its behavior, or onboard a new repo into it.

Working in a product repo here

• If tg-autopilot filed an issue and the diagnosis looks wrong or incomplete, treat it like any other bug report — comment or correct it, the automation doesn't need to be involved again.
• tg-autopilot needs write access to a repo for its PR/issue features to work in it; org default permissions already cover this for members, so no repo-level setup is normally needed.