Skip to content

blog: Add monthly updates post #3066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 5, 2025

Conversation

zapbot
Copy link
Contributor

@zapbot zapbot commented May 1, 2025

image

@psiinon
Copy link
Member

psiinon commented May 1, 2025

Logo
Checkmarx One – Scan Summary & Detailsa00b50a6-aa50-4a1e-b6de-b242550338e2

Great job, no security vulnerabilities found in this Pull Request

@ricekot ricekot force-pushed the monthly-updates-blog-post branch from 7eb60ae to 843bf54 Compare May 2, 2025 17:47
@ricekot ricekot marked this pull request as ready for review May 2, 2025 17:47
@psiinon
Copy link
Member

psiinon commented May 5, 2025

Looks great! Could split the first heading into 2 ("ZAP Wins Inaugural DefectDojo Award + a new Success Story!") and update to todays date? 😁

@ricekot ricekot force-pushed the monthly-updates-blog-post branch from 843bf54 to bef0ee7 Compare May 5, 2025 14:37
@ricekot ricekot force-pushed the monthly-updates-blog-post branch from bef0ee7 to 3726f0e Compare May 5, 2025 17:08
@kingthorin
Copy link
Member

Thanks!

Signed-off-by: zapbot <12745184+zapbot@users.noreply.github.com>
Signed-off-by: ricekot <git@ricekot.com>
@ricekot ricekot force-pushed the monthly-updates-blog-post branch from 3726f0e to c032932 Compare May 5, 2025 18:26
@kingthorin
Copy link
Member

That's fixed. I'm merging so we don't have to adjust dates 😀

@kingthorin kingthorin merged commit de819b9 into zaproxy:main May 5, 2025
3 checks passed
@thc202
Copy link
Member

thc202 commented May 5, 2025

Thank you!

@thc202
Copy link
Member

thc202 commented May 5, 2025

Why would we need to adjust dates?

@kingthorin
Copy link
Member

If it waited to 05/06

@kingthorin
Copy link
Member

I guess we could always merge late with it saying 05/05 anyway but still...

@thc202
Copy link
Member

thc202 commented May 6, 2025

The PR would have been merged either way.

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

Successfully merging this pull request may close these issues.

5 participants