-
Notifications
You must be signed in to change notification settings - Fork 514
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
[Blog] CNSC 2024 Takeaways #1315
Conversation
✅ Deploy Preview for tag-security ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this first blog coming to light. Let me know if you need any help with the failing actions.
442f5f2
to
373ea58
Compare
Looks like my LinkedIn link is returning a 999 status code... Is there a way to ignore this link? Or maybe we should treat 999 as a success? |
Signed-off-by: Shlomo Heigh <[email protected]>
I added the '999' status code to the links-config.json to be considered a success. |
Signed-off-by: Eddie Knight <[email protected]>
Signed-off-by: Eddie Knight <[email protected]>
@brandtkeller I'm getting unexpected behavior on the site... it's displaying the post even when the date is changed to the future. Do you have any ideas about that? A cursory google search didn't help, but I'll keep poking to see if I turn anything up. |
Looking into this currently (as time allows). Docs around blogs for |
Signed-off-by: Eddie Knight <[email protected]>
Description: As discussed in the TAG Security meeting on 2024-07-03, create a blog post with some highlights and takeaways from CloudNativeSecurityCon 2024.
See meeting notes, CloudNativeSecurityCon -> Highlights from the event (blog idea?)
Impact: To provide value to the community by sharing some of the learnings from the conference with those who couldn't attend, and to provide some review for those who did.
Sponsor:
If applicable mention a related issue or the related working group this blog originates from.Additional info: