* fix: transform json number item link
* docs(route/rsshub): use concrete json transform example
* Revert "docs(route/rsshub): use concrete json transform example"
This reverts commit e4d916451afa2207959312d999dfbc6c71919e55.
---------
Co-authored-by: jack <jack@example.com>
Co-authored-by: jack <jack@jacks-MacBook-Air.local>
* feat: add shanxi museum temporary exhibition route
* chore: trigger ci
* fix: remove pubDate if no return information
* fix: remove redundancy
* fix:fix the timezone error and refactor the resData and list
* fix: remove ! check for imgurl
* fix: remove empty message and add trycatch
* feat(route/sjtu): add CS school academic activities
* refactor(route/sjtu/cs/xshd): use JSX for description and respect dedicated item fields
- Switch to .tsx with renderToString (Rule 25)
- Move 时间→pubDate (with HH:mm), 报告人→author, 封面→image (Rule 11)
- Drop hand-written referrerpolicy attributes (Rule 39)
- pubDate now preserves hour/minute when source provides it
* fix(route/sjtu/cs/xshd): separate publish date from event time
- pubDate now reflects announcement publish date:
- in-site articles: detail page 发布日期 (authoritative)
- WeChat-redirect items: extracted from image URL path /upload/image/YYYYMMDD/
- 举办时间 (event time) moved back into description (no longer duplicates pubDate)
* fix(route/sjtu/cs/xshd): remove manual title trimming (Rule 16)
* fix(route/sjtu/cs/xshd): address review comments
- Use response URL to detect WeChat redirect
- Fetch WeChat MP content via fetchArticle
- Remove try-catch around detail requests
- Remove dangerouslySetInnerHTML from JSX rendering
* fix(route/sjtu/cs/xshd): use ofetch consistently
* fix(route/sjtu/cs/xshd): fallback on WeChat MP WAF errors
* fix(route/sjtu/cs/xshd): fallback when detail enrichment fails
The route enriches list items by fetching detail pages, but some SJTU
detail URLs are redirect stubs to WeChat MP. In CI, those intermediate
detail requests can fail with no response before the route reaches the
WeChat MP parser, causing Promise.all to reject and the whole feed to
return 503.
Switch detail enrichment aggregation from Promise.all to
Promise.allSettled and fall back to list-page metadata for only the
failed item. Successful items are still enriched with in-site article
content or WeChat MP content.
This follows the existing resilient detail-fetching pattern in
lib/routes/usenix/usenix.ts and keeps the scoped WeChatMpError fallback
around fetchArticle(), similar to lib/routes/wechat/sogou.ts.
* feat(route): add the Palace Museum route
* fix: fix trailing space, array and radar target
* fix: fix array
* fix: follow rule22
* refactor(dpm): migrate exhibitions route to JSX format (.tsx)
* fix(dpm): use arrow function in cheerio filter
* fix: update example
* fix: remove redundancy and fix error for endDate and fullduration
* chore: trigger gh actions retry
* fix: remove trim for fullduration
* fix:remove ! check for imgurl and fullduration
* fix: remove exhibition_item
* feat: add China National Museum exhibition route
* Update route.ts
* Update zl.ts
* Update zl.ts
* Update zl.ts
* fix: refactor to JSX and fix cache import
* fix: refactor to JSX, fix duration and fix import
* fix: replaceAll, if and regualr expression range
* Update zl.ts
* fix: refactor extra output and import namespace
* fix: fix error
* fix: adjust fullduration logic
* feat: refactor route file with type and subtype used
* fix: reduce the complexity
* fix: remove trim() for title
* fix: remove redundancy and fix error
* fix: remove toLowerCase redundancy
* fix: remove trim for title
* fix: Apply suggestions from code review and error fix
Co-authored-by: Tony <TonyRL@users.noreply.github.com>
---------
Here is a page with description-box:
https://www.cna.com.tw/news/aipl/202605070117.aspx
Explanation for the term 憲法第130條 is injected in the middle of a
paragraph and makes that paragraph hard to read. This change fixes that.
* route(gigazine): add English news full-text feed
Adds /gigazine/en route that fetches full article content from
GIGAZINE's English news listing. Uses sequential fetching with
delays to respect Cloudflare rate limits; subsequent loads are
served from cache.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* route(gigazine): improve english feed resilience
* test(gigazine): add english route coverage
* test(gigazine): move route coverage out of route tree
* test(api): cover route status cache fallbacks
* refactor(gigazine): apply PR review feedback to english route
- Use ofetch built-in auto-retry instead of hand-rolled circuit breaker
- Remove config.trueUA; let request-rewriter inject random browser UA
- Simplify Number.parseInt call (drop redundant ?? '' fallback)
- Update tests to match new retry and UA behaviour
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore: remove unrelated changes and unnecessary test file
* refactor(gigazine): simplify selectors and cleanup logic per review
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(route): support fulltext mode for nyaa
* feat(route): replace parameter name
* feat(route): migrate from query parameters to route paths
* feat(route): use mode=fulltext as trigger and update namespace
* delete fulltext routes
* feat(route): add /humanlayer/blog route
Add RSS feed for HumanLayer blog (www.humanlayer.dev/blog), scraping
blog listing and full article content with cheerio.
via [HAPI](https://hapi.run)
Co-Authored-By: HAPI <noreply@hapi.run>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* refactor(route): use CSS :not() selector instead of JS filter for humanlayer blog
Address PR review feedback: move /blog/tags/ exclusion into the CSS selector
instead of using a separate .filter() call.
via [HAPI](https://hapi.run)
Co-Authored-By: HAPI <noreply@hapi.run>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(route): extract tags into category field for humanlayer blog
Parse #-prefixed tags from the meta line and populate the category field.
via [HAPI](https://hapi.run)
Co-Authored-By: HAPI <noreply@hapi.run>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(route): address review feedback for humanlayer blog
- Remove redundant :not() selector (tag links use different class)
- Simplify tag extraction from parts.slice(3).join() to parts[3]
- Fix tag regex to match hyphenated tags like best-practices
via [HAPI](https://hapi.run)
Co-Authored-By: HAPI <noreply@hapi.run>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(route): remove custom limit for humanlayer blog, use built-in
via [HAPI](https://hapi.run)
Co-Authored-By: HAPI <noreply@hapi.run>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: HAPI <noreply@hapi.run>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: zj1123581321 <zj1123581321@users.noreply.github.com>
* feat(route): make GitHub pulls title and docs consistent with issues
I'm not really a coder, but I use RSSHub to bridge GitHub updates into IRC for my community. I noticed that the `pulls.ts` route didn't show the "Open/Closed" state in the feed title like the `issues.ts` route does, which was making my users a bit confused!
I tried my best to replicate the logic and metadata structure from `issues.ts` over to `pulls.ts`.
Changes:
- Updated the feed title to dynamically show the state (Open/Closed/All) and any labels.
- Updated the parameter metadata so the documentation looks as clean and organized as the Issues page.
I've tested this locally and it’s working perfectly for my IRC tracker. Hopefully, this helps keep things consistent across the GitHub routes!
Closes#21902
* Fix title formatting in pull request response