This repository was archived by the owner on Nov 26, 2020. It is now read-only.
configure vscode-rust in homu #902
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Whelp, this got lost in my notifications limbo. Sorry! Seems like the |
|
@pietroalbini is this succeeded by rust-lang/homu#117? |
|
Yes! Homu does not run on RCS anymore! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This attempts to setup bors for the https://github.com/rust-lang/vscode-rust repository, in preparation for the upcoming RLS/rust-analyzer extension merge.
Not sure if adding a secret is necessary here - I imagine we'd have a workflow where manually pushing a tag triggers a CI build and a deploy script pushing the release but that'd be something complementary to bors. Feel free to remove the secret config or let me know if I should remove that, thanks!