Mmyelinated-wackerowchore(search): defer crawl-config changes to their own PR
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
chore: consolidate discord links to /discord Every ethereum.org Discord link now points at the internal /discord/ path, with redirects.config.js holding the single canonical invite URL (https://discord.com/invite/ethereum-org). Links outside the Next.js site (README badges and prose, the GitHub issue template) use the full https://ethereum.org/discord/ instead. Invite links for other communities are untouched. This also repairs the /discord/ link mechanism added in fa519657b9. DISCORD_PATH had since been overwritten with an absolute discord.gg URL, which made isDiscordInvite (href.includes(DISCORD_PATH) && !href.includes("http")) unsatisfiable, so it returned false for every href. Restoring DISCORD_PATH to "/discord/" makes it resolve again, and the new DISCORD_URL constant gives page-jsonld.tsx the absolute form it needs now that isExternal("/discord/") is true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com> | 1 个月前 | |
fix(ci): gate weekly-release wait on required checks only The wait-for-pr-checks success gate evaluated the terminal/pending state of ALL checks on the PR, so the perpetually-PENDING Chromatic "UI Review"/"UI Tests" checks (which await manual approval) blocked success until the 3600s timeout. That fired the timeout branch and skipped the automated /review-release, even though every required check was green. When required_checks is set (and no single check_name), scope the pending/failure/success evaluation to just those checks. Chromatic approval remains a documented post-review manual step. required_checks still guards against false-success via the existing "missing" check (required checks that never posted). | 3 个月前 | |
feat: gh-aw intake automation — PR review, triage, and digest workflows (phase 1) Four agentic workflows (plus gh-aw's generated maintenance workflow) to improve intake throughput; baseline to beat is time-to-first-review P75 = 6.32 days. - pr-reviewer: lane-aware, verdict-first first-pass review of same-repo PRs with routing labels - backlog-sweeper: weekday sweep of the 8 oldest unreviewed PRs (forks included) with evidence-based recommend-close labels; never closes - issue-triager: labels-only classification of new issues; never comments - team-digest: weekday Discord digest of the PR/issue queue All agents run read-only (strict: true); writes go through allowlisted safe-outputs with per-run caps. Actions and containers are SHA-pinned. Prompts tuned via a read-only dry-run simulation against the live queue. | 2 个月前 | |
fix(intake): survive GraphQL 502s and stop the queue index truncating The collector piped `gh api graphql` straight into jq, so a transient 502 — observed three times in a few minutes — became a jq parse error and lost the whole morning's digest. Retry until the response is complete JSON with every page's `repository` present, and treat a failed mergeability refresh as non-fatal, since the records already carry a mergeState the agent is told to read as unverified. queue-index.jsonl replaces the pretty-printed queue-index.json: at ~2,700 lines the index truncated at an agent's file-read cap exactly like the detail files, dropping the newest third of the queue and reintroducing the blind spot it exists to close. One compact line per item is 140 lines for the same data, newest first so any truncation costs the least. | 2 个月前 | |
Merge remote-tracking branch 'origin/dev' into feat/typesense-search | 21 天前 | |
config: update codeowners, team | 4 个月前 | |
Remove screenshot section | 6 年前 | |
chore(ci): add dependabot config for security updates The repo had no dependabot.yml, so every advisory opened its own PR with no grouping and no way to scope what Dependabot touches. Version updates stay off. open-pull-requests-limit: 0 disables them, and security PRs are exempt from that limit, so advisories still open while minor/patch churn does not. Majors are raised as individual PRs regardless of a group's update-types, so leaving version updates on would let the 28 majors currently available saturate the limit and silently starve the grouped PRs. Advisories are grouped into a production and a development PR, so one unfixable advisory can't block the fixes bundled alongside it. No ignore block: with version updates off it could only mute advisories, including for the deps we hold back by hand (sharp, @netlify/plugin-nextjs). Those are decided per PR instead. The github-actions ecosystem is deliberately left out. It would rewrite the four generated gh-aw *.lock.yml workflows without updating their embedded manifests, and those files share actions with our hand-written workflows, so a name-based ignore can't separate the two. | 1 个月前 | |
deprecate: unused events code - Remove deprecated components and types - Remove legacy import system and package script - Remove legacy and data | 8 个月前 | |
chore: update release drafter labels | 2 年前 |