• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

rust-bitcoin / rust-bitcoin / 8849264030
83%

Build:
DEFAULT BRANCH: master
Ran 26 Apr 2024 01:45PM UTC
Jobs 1
Files 92
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

26 Apr 2024 01:44PM UTC coverage: 83.131%. Remained the same
8849264030

push

github

apoelstra
Merge rust-bitcoin/rust-bitcoin#2720: CI: Enable sync-labels for labeler

<a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/a03bc2e5b100b376876d2d5ab7425d7784c12930">a03bc2e5b CI: Enable sync-labels for labeler (Tobin C. Harding)

Pull request description:

  The `labeler` job has an input `sync-labels` (default `false`) that configures:

  > Whether or not to remove labels when matching files are reverted or no
  > longer changed by the PR

  ref: https://github.com/actions/labeler

  Currently we are using the default which means labels are not synced when a PR is modified.

  Example

  A PR initially touches the `hashes` and `bitcoin` crates and the labeler action adds `C-hashes` and `C-bitcoin`. Later, a force push removes the changes to `hashes`, the labeler will not remove the `C-hashes` label. Now the labels are incorrect.

  Note on `pull_request_target`:

  We use `on: pull_request_target`, this means the action is run in the target branch not in the PR branch. So the changes in this patch are not run when this PR is pushed up. Therefore we cannot test this patch but have to merge it blindly - please review carefully.

  Some further security notes that I learned while doing this patch. The `pull_request_target` has access to GitHub secrets, and in `manage-pr.yaml` we run `./contrib/gen_label_config.sh`. This is safe because its the version of this script on `master` that is run not the version in the PR (so a malicious attacker cannot patch `gen_label_config.sh` and have it be run). However we need to be aware that we do not accidentally merge some funky shell and inadvertently leak secrets.

ACKs for top commit:
  storopoli:
    ACK a03bc2e5b100b376876d2d5ab7425d7784c12930
  apoelstra:
    ACK a03bc2e5b100b376876d2d5ab7425d7784c12930

Tree-SHA512: 4082e52edc1d6ae55517dd2ec3ffb35965f

19195 of 23090 relevant lines covered (83.13%)

16809.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 8849264030.1 26 Apr 2024 01:45PM UTC 0
83.13
GitHub Action Run
Source Files on build 8849264030
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #8849264030
  • c4d017e7 on github
  • Prev Build on master (#8848443585)
  • Next Build on master (#8867463429)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc