-
Notifications
You must be signed in to change notification settings - Fork 998
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
1.4 release and kubecon blog for demo #2608
Conversation
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.
Content wise it LGTM 🤩
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.
happy to have that, looks good to me content-wise, please make sure that you fix the formatting
❗ Planning on adding a header picture. Please don't merge until it's added ❗ |
It wasn’t ready to merge @austinlparker |
Whoops! It was approved and all comments were resolved? Can you make a new PR with whatever changes were left?Sent from my iPhoneOn Apr 18, 2023, at 7:39 AM, Carter Socha ***@***.***> wrote:
It wasn’t ready to merge @austinlparker
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Ok, I missed the comment, my bad. In my defense it's early. |
This reverts commit 4b0f105.
All good. I’ll just update later and then point to it |
You'll need to create a new PR -- sorry, I saw your message in Slack to revert and did so. |
No description provided.