- Notifications
You must be signed in to change notification settings - Fork1k
chore: add a test commit (don't merge)#892
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
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.
this is amazing! merge this immediately!!!! 🚀
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.
LGTM, looking forward to Joe managing all my tunnels
cc@kylecarbs or anyone else: CI jobs still haven't run. Is that expected? |
Merge in |
Hmm...is that the desired behavior we want? I wouldn't think so because then we'd have to merge community code before knowing if it passes all our checks. |
I may have misunderstood this. I am guessing you meant "merge in main" as in "update your branch with main". Let's see if it works! |
Discussed with@kylecarbs - we're not sure why CI isn't running. We're going to revisit this once we flip the switch and make this public. |
This is a test from a forked repo of
coderto ensure that CI checks run as expected.#653