Repository navigation
OSS-Fuzz: Move fuzzer to upstream repository - #1724
arthurscchan wants to merge 7 commits into
Conversation
Signed-off-by: Arthur SC Chan <arthur.chan@adalogics.com>
[Low impact] The PR appears safe to merge; no new actionable issue was found.
|
Signed-off-by: Arthur SC Chan <arthur.chan@adalogics.com>
Signed-off-by: Arthur SC Chan <arthur.chan@adalogics.com>
Coverage Report for CI Build 39566034341Coverage remained the same at 89.907%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
baylesj
left a comment
There was a problem hiding this comment.
Thanks for addressing the automatic greptile feedback. I did a more extensive review and have some asks before landing this in JsonCpp.
|
Thanks for the comments. Please spare me a few days to address those comments as I am stucked in some other things now. I will address them asap. Sorry for the delay. |
Signed-off-by: Arthur SC Chan <arthur.chan@adalogics.com>
|
Want your agent to iterate on Greptile's feedback? Try greploops. |
This PR moves all the OSS-Fuzz fuzzers to the upstream storage for easier management. This PR works together with OSS-Fuzz (google/oss-fuzz#16308) to accommodate the moving of fuzzers upstream.
Of course, this is only a suggestion. If the maintainers would prefer the fuzzers to remain in OSS-Fuzz, I am happy to keep the current setup and to ping the relevant maintainers for review whenever I add new fuzzers later in the process.
Thank you for considering this, and I would welcome any feedback on the preferred approach.
Remark: After this PR is accepted and merged, there will be additional PRs for adding new fuzzers for this project later.