Dylan M. Taylor
d3c8210144
ci: verify the actions lockfile in CI
...
Fails the build when .github/workflows/actions.lock stops matching the
workflows, or when a locked pin no longer verifies upstream, so a stale or
tampered lockfile cannot go unnoticed between dependency updates.
2026-11-12 07:23:03 -05:00
Dylan M. Taylor
abcff955d3
ci: lock workflow actions through an actions.lock lockfile
...
Mutable action tags are a supply-chain risk: a moved tag runs different code
without a diff. Every workflow action is now pinned through
.github/workflows/actions.lock, and CI verifies the lockfile so an out-of-sync
or tampered one fails instead of running.
2026-11-12 07:19:04 -05:00
Dylan M. Taylor
7f2a7add80
Sonar: numeric sort for the oldest queued item, explicit migration order, linear trailing-space trim ( #3 )
2026-11-10 22:57:58 -05:00
Dylan M. Taylor
9374091047
ci: SonarCloud analysis from CI, like the other craft repos ( #2 )
...
* ci: SonarCloud analysis from CI instead of automatic analysis
* Publish vitest coverage to SonarCloud (test:coverage, @vitest/coverage-v8)
* ci: shared SonarCloud workflow back on @main (node coverage merged in craft-common-actions#194)
2026-11-10 22:33:01 -05:00
juansebsol
4818112b37
npm audit fix: fastify 5.12.8, @fastify/static 10.1.10, fast-uri
2026-11-10 18:52:23 -08:00
juansebsol
5e51741ee9
Ticket panel: an optional description for each group button
2026-11-10 18:26:59 -08:00
Dylan M. Taylor
76e1368b97
Sonar: clear 63 of the 65 open issues ( #1 )
...
Behaviour-preserving rewrites of the regex, promise, sort, reduce, default-parameter, control-character and migration findings. See the pull request for each.
2026-11-10 18:45:36 -05:00
juansebsol
91c74a198a
Ticket panel: a group button always opens its list, even with one app
2026-11-10 12:29:56 -08:00
juansebsol
592b9f8b48
Ticket panel: a button for the main's apps and one for linked workspaces' apps, each opening its own list
2026-11-10 12:02:43 -08:00
juansebsol
baa30135e9
Ticket panel: a menu for each workspace, named after it or as set on the Panel page
2026-11-10 11:47:44 -08:00
juansebsol
6b4ee4ce3e
Overview uses the full page width; fix test typings
2026-11-10 07:59:01 -08:00
juansebsol
e62013067f
README: analytics screenshot on top, Discord panel under features
2026-11-10 07:55:02 -08:00
juansebsol
8bd8b15288
README: center the header, intro and panel screenshot
2026-11-10 07:49:08 -08:00
juansebsol
9b33275a43
License: MIT (LICENSE file, package.json, README)
2026-11-09 18:55:02 -08:00
Dylan M. Taylor
7643e2c844
Add Dockerfile based on DHI Node and docker-publish workflow using craft-common-actions
2026-11-09 20:38:45 -05:00
juansebsol
a0d2cd3f50
Global admins: admins in every linked workspace (a switch on admin invites and roles like moderators, off by default; today's admins and unused admin invites are global); a linked workspace can have admins of its own, made by the owner from someone's row or an invite, the higher role counting; its admins invite and remove its moderators; people only in a linked workspace don't see Deployment or Server health
2026-11-09 16:35:41 -08:00
juansebsol
4c9fd006be
Workspace menu: New linked workspace… for the main workspace's owner and admins (from a linked workspace too), with a name and what it is, then it opens
2026-11-09 16:06:12 -08:00
juansebsol
271e02ddfb
Linked workspaces: a workspace for apps in another GitHub organization, made from Settings, with its own GitHub connection, apps, tickets, triage and analytics, using the main's Discord server; its apps go on the main's panel (after the main's) or a panel of its own, and My tickets shows tickets from both; the main's admins are its admins and its global moderators (a new switch on moderator invites and roles, on for today's moderators) are its moderators, and it can invite moderators of its own; an install link lets an organization's owner install the GitHub App without an account
2026-11-09 15:53:18 -08:00
juansebsol
3376d32462
My tickets: members can add details, add screenshots or close one of their own open tickets from its page (each off until switched on in Panel, with the GitHub comment for each); details and screenshots go on the issue inside the admins' comments, a close is in the Mod log as the reporter's and moderators can undo it; not offered when other reports follow the ticket; 5 updates an hour per member; the ticket's story shows what they did
2026-11-09 14:51:34 -08:00
juansebsol
51f5f03429
My tickets: open tickets under an Open heading and closed ones under a Closed heading, one line each with the title not bold; clearer closed icons (not planned, same as another report, removed); counts in the headings instead of the footer
2026-11-09 10:24:03 -08:00
juansebsol
db77d5a9e3
Discord tickets › Panel › My tickets (off by default): the panel shows Open a ticket (the app menu privately, or straight on with one app) and My tickets, where each member privately sees the tickets they sent here, open ones first, with what's happening with each in the known-issues board's words (plus needs more information, closed, being sent), a repeat following the report it's the same as, and each ticket's story (filed, same problem as, fix started or finished, released) with Back and Open on GitHub; no links for private repositories; the board and My tickets share one status function
2026-11-09 10:01:37 -08:00
juansebsol
0b8f436b0e
Discord tickets › Panel: a Privacy notice section to word who can read a report and what to leave out, for public and private repositories (each naming its apps), shown when members choose a ticket type and at the top of the form, live right away without publishing; empty or Reset to default brings back the built-in text
2026-11-04 20:58:51 -08:00
juansebsol
5e16960de3
Analytics › Platforms: most downloaded first, like the other breakdowns (each keeps its colour; the chart's stacks keep their fixed order)
2026-10-31 16:22:20 -07:00
juansebsol
023a777add
Analytics › Platforms: FreeBSD and Web on their own instead of inside Other, in the Platforms card and the downloads chart, each in its own colour (FreeBSD and Web only when they have downloads)
2026-10-31 16:19:05 -07:00
juansebsol
ebabb0f986
MCP: tools in Read and Write groups, each with its own switch in Members & permissions; Read & write or Read only tokens for people who can write (read-only for everyone else); what your agent can do in two columns; a Docs tab with setup, examples, ready-made prompts, every tool, claims, safety and troubleshooting
2026-10-29 18:24:18 -07:00
juansebsol
b108ce6b15
MCP: coding agents (Claude Code, Cursor, VS Code, Codex) connect to POST /mcp with a personal token (shown once, stored hashed, expiring, revocable, read-only option) and work with tickets as their person: find and count tickets with filters, read a ticket with its history, triage, repeats, screenshots and pull requests, find what's related to a ticket, a pull request or text, pull requests, releases, Knowledge, the Mod log, claims, and close, reopen, mark duplicates, labels and saved replies (logged as via MCP, undo); each tool a switch per moderator in Members & permissions, apart from the pages; off until an admin turns it on; ready-made prompts; claims shown in Ticket management
2026-10-29 17:46:29 -07:00
juansebsol
c04353245a
Moderation › Ticket management loads at once: the lists find each issue's ticket by an index (13 s to under 0.1 s with 10,000 open issues), GitHub's side of a ticket is kept encrypted and shown at once, read again in the background when over a minute old with a note if it changed, the next two in the list are read ahead, and copies are dropped 30 days after they were last read
2026-10-28 15:58:18 -07:00
juansebsol
0857020514
Moderation: Ticket management (open tickets and issues from Discord and GitHub in lists: Repeat bugs grouped under the original with its fix, Fixed but open, Needs info and quiet, Spam, Old, Closed by mods; the open one with its whole history, triage's verdict, similar issues, Open in Discord and on GitHub; close for a reason, reopen, undo for 15 minutes, mark or unmark duplicates, saved replies, labels, several at once in the background, keys J/K/C/D/R), Mod log, and Replies & reasons where admins write what's posted; off until an admin turns it on, each page in the access map
2026-10-28 14:37:25 -07:00
juansebsol
c33ea289f8
AI triage › Overview: what triage did right under the period it counts, and the labels on open issues last, under a Right now on GitHub divider
2026-10-28 11:36:42 -07:00
juansebsol
83b052b0c9
AI triage › Overview: what triage did as one grouped table like the labels (actions applied and waiting in Review, priority it gave, how sure it was, skipped, by app), every bar on the same scale, with a filter by group
2026-10-28 11:28:47 -07:00
juansebsol
736d4f55f4
AI triage › Overview: labels on open issues as one table, a group per category with its coverage and backfill, every bar out of all open issues, a category filter and label search; bars are drawn in SVG since the CSP blocked their inline widths (Overview, Custom labels, Re-run)
2026-10-28 11:04:41 -07:00
juansebsol
43e8b22d89
Bot features: a row per feature (Known-issues board, GitHub releases) with its switch and a gear that opens it; GitHub releases move here from Announcements; Announcements is now writing messages the bot posts in the channels you pick, with a card, buttons and a ping, changed or deleted everywhere at once
2026-10-27 17:26:01 -07:00
juansebsol
6681957978
Bot features: Known issues on one page, a card with what the board is, its status, on/off and publish, then the issues and each part of the settings as closed rows that open to edit; each row saves only its own part
2026-10-27 16:52:11 -07:00
juansebsol
ecbddd50ff
Custom labels: a closed row per category (name, how many Claude picks, what it's about, its labels with their open issues, modes, how many are labelled) that opens into its editor
2026-10-27 15:01:14 -07:00
juansebsol
2382b3d335
Re-run: what a run costs before Start (and in its confirmation), so far and when done while it runs; triage costs count tokens read from Claude's cache at their own price
2026-10-27 13:31:16 -07:00
juansebsol
1abd95b581
AI triage: Custom labels (renamed from label groups, a row per label with open-issue counts), backfill them on open tickets and issues from Re-run (labels only), and an Overview tab with every label on open issues and what triage did
2026-10-27 13:12:23 -07:00
juansebsol
877400a988
Bot features: a known-issues board in Discord, kept up to date with the most-reported problems and their status (looking into it, being worked on, fix coming, fixed in a release), with pins, hides, titles and notes per issue
2026-10-23 10:21:39 -07:00
juansebsol
78480d467f
Announcements: buttons are your own (label, link and app each; links can be a web address, the release, or one of its files found by name), and the release notes button can be renamed or turned off
2026-10-22 19:41:13 -07:00
juansebsol
fc03b2b41e
Announcements: post each app's new GitHub releases in Discord, with Claude-written notes, review-first or automatic posting, per-app channel and role, and an opt-in pings panel
2026-10-22 13:08:02 -07:00
juansebsol
20ddb64723
Analytics: count stars from GitHub's star count every 30 minutes (the stargazer list is refused for the app), show a refused read on the page, and treat partial GraphQL answers as failures (Repo status logs them)
2026-10-22 11:08:37 -07:00
juansebsol
d9df831bc9
Analytics: draw the bar lists as real horizontal bar charts (one axis from zero, names on the left, values and shares at the tips, never stretched)
2026-10-22 08:42:52 -07:00
juansebsol
ca9403df9b
Reorder the tools: Analytics, Repo status, Discord tickets, GitHub issues, AI triage, Contributor roles (sidebar, Overview and Members & permissions)
2026-10-21 22:29:07 -07:00
juansebsol
a80185f236
Analytics: an All range first, with lifetime totals (GitHub's own download and star counts, every ticket, issue and merged pull request), per-app rankings instead of the timeline, and the steps greyed out
2026-10-21 21:32:37 -07:00
juansebsol
450a768bf6
Analytics: call tickets Discord tickets, and show how many issues opened came from Discord and how many were opened on GitHub
2026-10-21 21:26:05 -07:00
juansebsol
9dc4ceeacd
Analytics: star totals recorded every 30 minutes with the downloads (GitHub's own count), and the main chart switches between downloads and stars, with each app's total and new stars
2026-10-21 20:58:49 -07:00
juansebsol
f534574239
Contributor roles: count merged pull requests from the pull request index (read again just before each check) instead of GitHub's issue search, which leaves pull requests out without Pull requests: Read; keep merged pull requests for good; ask to try again rather than say no when a repository's pull requests couldn't be read
2026-10-21 12:03:51 -07:00
juansebsol
07145daf17
Analytics: downloads recorded every 30 minutes (per app, platform, processor, format and version), with tickets, issues, pull requests and stars over the same time, release health (tickets per 1,000 downloads), ranges from today to 12 months and steps from 30 minutes to a day, in the viewer's time zone; off until turned on
2026-10-21 09:22:53 -07:00
juansebsol
50bb5985fd
Pull requests: read them from GitHub's pull request list (the issue list leaves them out without Pull requests: Read; public repositories' list works without it), on their own every 10 minutes after a catch-up, never failing the issue sync; the Pull requests tab says how far reading got, what went wrong, and when the background process is out of date
2026-10-20 23:57:43 -07:00
juansebsol
5f5569bb64
Pull requests: kept from the issue sync (open, and merged in the last 90 days, with the issues each is for and the release each fix shipped in); AI triage gets Being worked on and Already fixed (off by default) to say a ticket is in progress in a PR or already fixed, with or without a release; Repo status gets a Pull requests tab and shows the PR on issues in Fix first and Most reported
2026-10-20 22:55:26 -07:00
juansebsol
26dd9d211f
Repo status: Most reported tab ranks issues by the Discord tickets about them (duplicates count for their original, unreviewed suggestions shown as waiting for review), by repository and period, with each issue's tickets, people, GitHub duplicates and reports since it was closed
2026-10-20 15:56:04 -07:00