Skip to content

Fix fuzzer issue template#6963

Open
connortsui20 wants to merge 1 commit intodevelopfrom
ct/fuzz-template-cmd
Open

Fix fuzzer issue template#6963
connortsui20 wants to merge 1 commit intodevelopfrom
ct/fuzz-template-cmd

Conversation

@connortsui20
Copy link
Contributor

Summary

From #6936 I do not understand why we are so against being descriptive in these templates given most of what claude says is complete nonsense. If we want concision, the reproduction steps still need to make sense.

This changes the fuzzer template to have 2 different details sections, one with a full and correct description of how to reproduce, and the other with a single command for people who know what they are doing. The maintainers do not need to look at the first section.

Testing

N/A

Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
@connortsui20 connortsui20 added the changelog/chore A trivial change label Mar 13, 2026
@connortsui20 connortsui20 changed the title fix fuzzer issue template Fix fuzzer issue template Mar 13, 2026
@codspeed-hq
Copy link

codspeed-hq bot commented Mar 13, 2026

Merging this PR will improve performance by 18.36%

⚡ 2 improved benchmarks
✅ 1007 untouched benchmarks
⏩ 1515 skipped benchmarks1

Performance Changes

Mode Benchmark BASE HEAD Efficiency
Simulation bitwise_not_vortex_buffer_mut[1024] 535.6 ns 477.2 ns +12.22%
Simulation bitwise_not_vortex_buffer_mut[128] 376.1 ns 317.8 ns +18.36%

Comparing ct/fuzz-template-cmd (3e81753) with develop (8ac7234)

Open in CodSpeed

Footnotes

  1. 1515 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/chore A trivial change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant