<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>标签：网站-GitHub - 皓子的小站</title><link>https://howiehz.top/tags/github</link><atom:link href="https://howiehz.top/tags/github/feed/tags/github.xml" rel="self" type="application/rss+xml"/><description>An Island on the Internet</description><generator>Halo v2.24.0</generator><language>zh-cn</language><image><url>https://howiehz.top/upload/haozi-logo.png</url><title>标签：网站-GitHub - 皓子的小站</title><link>https://howiehz.top/tags/github</link></image><lastBuildDate>Tue, 21 Apr 2026 01:12:34 GMT</lastBuildDate><item><title><![CDATA[自动追踪 Oxlint 对 ESLint 规则的新增支持]]></title><link>https://howiehz.top/archives/eslint-migration-auto-track-oxlint-rules</link><description><![CDATA[<img src="https://howiehz.top/plugins/feed/assets/telemetry.gif?title=%E8%87%AA%E5%8A%A8%E8%BF%BD%E8%B8%AA%20Oxlint%20%E5%AF%B9%20ESLint%20%E8%A7%84%E5%88%99%E7%9A%84%E6%96%B0%E5%A2%9E%E6%94%AF%E6%8C%81&amp;url=/archives/eslint-migration-auto-track-oxlint-rules" width="1" height="1" alt="" style="opacity:0;">简体中文 | English 两个月前我写了一篇 ESLint 到 Oxlint 渐进式迁移快速上手指南，里面提到了 Oxlint 官方提供的迁移工具，用于将 ESLint Flat Config 配置转换为 Oxlint 配置。 几个月来 Oxlint 逐渐实现了许多原先不支持的规则，执行迁移工具]]></description><guid isPermaLink="false">/archives/eslint-migration-auto-track-oxlint-rules</guid><dc:creator>HowieHz</dc:creator><category>前端工具链</category><pubDate>Sat, 22 Nov 2025 08:51:03 GMT</pubDate></item><item><title><![CDATA[解决 Docker pull image "ghcr.io..." Unauthorized error]]></title><link>https://howiehz.top/archives/solve-docker-pull-image-ghcr-unauthorized-error</link><description><![CDATA[<img src="https://howiehz.top/plugins/feed/assets/telemetry.gif?title=%E8%A7%A3%E5%86%B3%20Docker%20pull%20image%20%22ghcr.io...%22%20Unauthorized%20error&amp;url=/archives/solve-docker-pull-image-ghcr-unauthorized-error" width="1" height="1" alt="" style="opacity:0;">此文章有英文版本/This article is available in English 现象 解决方法 之前构建的时候一切顺利，在笔者要写教程的时候，构建后拉取时不断报错Unauthorized https://github.com/orgs/[XXX]/packages/container/[]]></description><guid isPermaLink="false">/archives/solve-docker-pull-image-ghcr-unauthorized-error</guid><dc:creator>HowieHz</dc:creator><category>容器化</category><pubDate>Mon, 25 Mar 2024 13:37:00 GMT</pubDate></item><item><title><![CDATA[解决 GitHub Actions push to ghcr '403 Forbidden' error]]></title><link>https://howiehz.top/archives/solve-github-action-push-to-ghcr-403-error</link><description><![CDATA[<img src="https://howiehz.top/plugins/feed/assets/telemetry.gif?title=%E8%A7%A3%E5%86%B3%20GitHub%20Actions%20push%20to%20ghcr%20%27403%20Forbidden%27%20error&amp;url=/archives/solve-github-action-push-to-ghcr-403-error" width="1" height="1" alt="" style="opacity:0;">此文章有英文版本/This article is available in English 现象 github action 对应 workflow 运行时报错 解决方法 之前构建的时候一]]></description><guid isPermaLink="false">/archives/solve-github-action-push-to-ghcr-403-error</guid><dc:creator>HowieHz</dc:creator><category>交付体系</category><pubDate>Mon, 25 Mar 2024 13:11:00 GMT</pubDate></item><item><title><![CDATA[解决 Umami API 更新延迟问题(如何修改开源项目代码并构建 Docker 镜像-以 Umami 为例)]]></title><link>https://howiehz.top/archives/umami-api-latency-issues</link><description><![CDATA[<img src="https://howiehz.top/plugins/feed/assets/telemetry.gif?title=%E8%A7%A3%E5%86%B3%20Umami%20API%20%E6%9B%B4%E6%96%B0%E5%BB%B6%E8%BF%9F%E9%97%AE%E9%A2%98%28%E5%A6%82%E4%BD%95%E4%BF%AE%E6%94%B9%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%E4%BB%A3%E7%A0%81%E5%B9%B6%E6%9E%84%E5%BB%BA%20Docker%20%E9%95%9C%E5%83%8F-%E4%BB%A5%20Umami%20%E4%B8%BA%E4%BE%8B%29&amp;url=/archives/umami-api-latency-issues" width="1" height="1" alt="" style="opacity:0;">现象 umami版本为 v2.10.2 如果未来版本依然没有更改的话那这个问题应该还是存在 当使用 GET /api/websites/{websiteId}/active 这个 API 的时候，发现有至少 1 分钟以上的延迟，经过一个简单的测试脚本，发现本地刷新就存在延迟。 解决过程的大纲 笔者向]]></description><guid isPermaLink="false">/archives/umami-api-latency-issues</guid><dc:creator>HowieHz</dc:creator><category>容器化</category><pubDate>Mon, 25 Mar 2024 12:40:00 GMT</pubDate></item></channel></rss>