-
Notifications
You must be signed in to change notification settings - Fork 130
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
chore: move washboard to its own directory #764
chore: move washboard to its own directory #764
Conversation
Yes please, until we have a release process |
43dab62
to
0b579ee
Compare
fix: specify version of wash-lib
On second thought, I'll leave this in draft until we've archived the wash repo. I don't want to make it more difficult to cherry-pick changes from there |
0b579ee
to
6688b14
Compare
6688b14
to
23dceed
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.
I'm very surprised that using the relative path to parent directory for the washboard worked here
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.
Looks good w/ Lachlan's request
23dceed
to
2cc4378
Compare
Signed-off-by: Connor Smith <connor.smith.256@gmail.com>
2cc4378
to
5292cbe
Compare
Looks like you forgot to update the |
Feature or Problem
This is the minimal amount of work to split the
washboard
directory out ofwash
into its own top-level directoryThe washboard doesn't have any CI yet
@lachieh should I commit changes to
dist/
?Testing
Manual Verification
cd washboard && make build-ui && cd -
cd wash && cargo build
./target/debug/wash up --nats-websocket-port 4001
./target/debug/wash ui --experimental