mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[PR #1967] [MERGED] untrack fuzz/Cargo.lock #2727
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#2727
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/hickory-dns/hickory-dns/pull/1967
Author: @bluejekyll
Created: 6/11/2023
Status: ✅ Merged
Merged: 6/12/2023
Merged by: @bluejekyll
Base:
main← Head:untrack-fuzz-lock📝 Commits (1)
88a17aauntrack fuzz/Cargo.lock📊 Changes
2 files changed (+1 additions, -576 deletions)
View changed files
📝
.gitignore(+1 -0)➖
fuzz/Cargo.lock(+0 -576)📄 Description
I don't think this is necessary, we can always add it back if the fuzz build becomes unstable. It's annoying to keep in sync at the moment.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.