Skip to content

Conversation

@nickelc
Copy link
Contributor

@nickelc nickelc commented Feb 13, 2021

The reason to choose setup-rust-action over action-rs/* is that the action already comes with problem matchers for error, warning & cargo. This makes actions-rs/cargo obsolete and the workflow less verbose.


steps:
- uses: actions/checkout@v2
- uses: hecrj/setup-rust-action@v1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason not to use actions-rs/..?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, for being 🦥 . I've updated the PR comment.

@seanmonstar
Copy link
Member

Thanks for explaining some. The reason I ask is that unless there's a significant reason otherwise, it makes sense to me to keep things similar across hyper, h2, http, etc. Does that seem reasonable? Is there places in the Rust ecosystem that are shifting from actions-rs to this one?

@nickelc
Copy link
Contributor Author

nickelc commented Feb 16, 2021

I think the setup-rust-action action came first but here we go now with actions-rs/*.

@seanmonstar seanmonstar merged commit f8ae762 into hyperium:master Feb 16, 2021
@nickelc nickelc deleted the ci-actions branch February 16, 2021 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants