[中] CI 没有运行 telemetry 的 Rust 单元测试

Open Beginner friendly
#49 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, rust
Domain
ci-cd

Research direction

Read the existing steps around .github/workflows/release.yml:61-63 and .github/workflows/windows.yml:59-62 to see where the build runs, and compare with the command in tools/telemetry/README.md:56. Run cargo test --locked --manifest-path tools/telemetry/Cargo.toml locally first to confirm it passes, then add it as a step to the workflows (the issue notes the Mac runner already has Rust). Done means a PR touching the telemetry main.rs test triggers that command in CI.

Written by the indexing model from the issue text.

Description

位置:tools/telemetry/README.md:56;.github/workflows/release.yml:61-63;.github/workflows/windows.yml:59-62

现象:README 给出 cargo test --locked --manifest-path tools/telemetry/Cargo.toml,但三个 workflow 都没有这一步。main.rs 内的 Rust 测试因此从未进入 CI。

建议:至少在完整构建中加入该命令(Mac runner 已带 Rust)。

来源:2026-11-15 全仓只读审计,PR #7 未包含此项。

Dominant language
Swift
Stars
2
Forks
2
Avg merge
1h 11m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cyandee/BirdLock

All issues in cyandee/BirdLock

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.