-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(examples): Migrates remaining go examples from monorepo #53
feat(examples): Migrates remaining go examples from monorepo #53
Conversation
As a note, I only updated docs of the examples I moved over. My next follow up will be updating the docs for the other examples |
8e1f3a4
to
73b33ea
Compare
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.
We need to figure out a different way to handle deploying the components if that's something that's going to be tested as part of the pipeline, the bash script that's used in the main repository is super flaky and I would rather not introduce that into this repo's CI.
b8988ff
to
f1fb78a
Compare
This moves the two examples that weren't moved from the monorepo. This also adds tests and adds simple smoke tests for each component. I also modified the examples job to run once per week to ensure things don't go stale with new versions of `wash` Signed-off-by: Taylor Thomas <[email protected]>
f1fb78a
to
2560a87
Compare
For reference, I was looking at many of the recent flakes in the main repo and all of them seem to fail with
I think my new way of doing it solves this issue |
…er examples Signed-off-by: Taylor Thomas <[email protected]>
c3acea5
to
69ec4cc
Compare
This moves the two examples that weren't moved from the monorepo. This also adds tests and adds simple smoke tests for each component. I also modified the examples job to run once per week to ensure things don't go stale with new versions of
wash