Use spec.creationTime consistently for reply timestamps

[Copilot]

Replies used metadata.creationTimestamp while comments used spec.creationTime. Since metadata.creationTimestamp doesn't necessarily represent the actual creation time, both should use spec.creationTime.

Changes:

• Updated reply-item.ts line 122 to use reply?.spec.creationTime instead of reply?.metadata.creationTimestamp

// Before
.creationTime="${this.reply?.metadata.creationTimestamp ?? undefined}"

// After  
.creationTime="${this.reply?.spec.creationTime}"

This aligns replies with comments, which already use spec.creationTime.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• pkg.pr.new
  • Triggering command: /usr/local/bin/node node /usr/local/bin/pnpm install (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>回复的时间不正确</issue_title>
<issue_description>目前项目中回复采用的时间是 metadata. creationTimestamp

plugin-comment-widget/packages/comment-widget/src/reply-item.ts

Line 122 in bf6435b

.creationTime="${this.reply?.metadata.creationTimestamp ?? undefined}"

但评论采用的时间又是 spec. creationTime

plugin-comment-widget/packages/comment-widget/src/comment-item.ts

Line 120 in bf6435b

.creationTime="${this.comment?.spec.creationTime}"

应当使其保持一致，建议统一使用 spec. creationTime， metadata. creationTimestamp 并不一定代表真实的创建时间。</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes 回复的时间不正确 #206

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ruibaby]

/lgtm

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ruibaby

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ruibaby]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment