Repository navigation
Conversation
…e default highlight theme
fix: fix copyright script logic
Switch diff code's highlights from bg highlights to text highlights
深浅色切换优化 / 修复加载闪屏
添加timeline功能
timeline功能。用法:(貌似markdown识别有点问题
{% timeline %}
{% timenode 2024-04-15 %}
这是第一个时间点的内容。
测试包含**Markdown格式**的文本。
- 列表项1
- 列表项2
> 引用内容

{% endtimenode %}
{% timenode 2024-04-16 %}
这是第二个时间点的内容。
{% endtimenode %}
{% timenode 2024-04-17 %}
这是第三个时间点的内容。
{% endtimenode %}
{% endtimeline %}
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6ae2dd4ee7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| registry-url: https://registry.npmjs.org/ | ||
|
|
||
| - run: npm install | ||
| - run: npm ci |
There was a problem hiding this comment.
Supply a committed lockfile before switching releases to npm ci
When a release is created, .github/workflows/release.yml now runs npm ci immediately after checkout/setup, but a repository-wide tracked-file search finds neither package-lock.json nor npm-shrinkwrap.json, and no preceding step generates one. npm's ci documentation explicitly states: “The project must have an existing package-lock.json or npm-shrinkwrap.json.” Consequently, the release job fails at installation and never reaches publication. Commit a matching lockfile or retain npm install.
Useful? React with 👍 / 👎.
| const post_word_count = page_type === 'post' ? keepWordCount(post.content) : 0 | ||
| const post_min2read = page_type === 'post' ? keepMin2Read(post.content) : 0 |
There was a problem hiding this comment.
Restore the configuration guards for post word-count metadata
For sites with word counts or reading times disabled—including the supplied defaults—these calculations now run for every post, and the subsequent conditions render their results without checking either configuration switch. Nonempty posts therefore display both metrics despite post.word_count.word and post.word_count.min2read being false; keepMin2Read even returns at least 1 for empty content. Gate each calculation or rendered span on its corresponding option, preserving compatibility with the existing wordcount setting when migrating its name. This violates the configuration-default preservation requirement in AGENTS.md.
AGENTS.md reference: AGENTS.md:L17-L17
Useful? React with 👍 / 👎.
No description provided.