-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Rust crate #57
Rust crate #57
Conversation
Were you able to test this? |
Testing wise, cargo build definitely works. I can actually add a unit test. What I haven't tested is the cargo publishing stuff but I obviously cannot test that yet very easily. |
This also means, that I need to get to #52 (or hope somebody else can help) |
Sorry this has been so messy. I guess working on CI config often leads to messy pull requests but I think we are getting there now. |
Dry run publishing looks good to me https://github.com/Razzeee/tree-sitter-elm/runs/1432779911?check_suite_focus=true |
Don't worry, I don't think that this is messy
…On Fri, Nov 20, 2020, 19:51 Harry Sarson ***@***.***> wrote:
Dry run publishing looks good to me
https://github.com/Razzeee/tree-sitter-elm/runs/1432779911?check_suite_focus=true
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNLEZAPEV46L2MILWVKWK3SQ23DTANCNFSM4TY4Y2XA>
.
|
Next step is to remove the dry run flag but still run publish on pull requests and see if 4.3.1 gets released I think. |
Maybe I should add some docs first |
I'll merge this and try to release a new version with the only change, that we get a rust version out of this. |
A possible implementation of #54. Includes a sketch of what automated releases might look like.