🐛 fix: stop run CI in forked repo

[gouzil]

fix

• ci 在 fork repo 上运行

[Copilot]

Pull Request Overview

This PR aims to ensure CI jobs run only in the main repository and removes the uv.lock file.

• Adds a repository check to the lint-and-fmt workflow
• Deletes the uv.lock file

Comments suppressed due to low confidence (1)

.github/workflows/lint-and-fmt.yml:12

• This if condition restricts the job to the main repo, which prevents CI from running on forks. To enable CI in forked repositories, consider removing this condition or adjusting it to detect and allow forks explicitly.

    if: github.repository == 'PFCCLab/google-yamlfmt'

[SigureMo]

为什么要删掉 lockfile？一般 lockfile 是需要存在 repo 里的，确保可复现性

[gouzil]

行，我考虑的是，因为编译产物并不会在这里，所以这个可复现是不稳定的。

[SigureMo]

这里主要是编译依赖吧，主要能保证 CI 编译环境能一致

[SigureMo]

标题里应该是 stop run CI in forked repo？