Skip to content
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

Add command/task runner #3

Closed
calebcartwright opened this issue Dec 28, 2018 · 1 comment
Closed

Add command/task runner #3

calebcartwright opened this issue Dec 28, 2018 · 1 comment
Assignees
Labels
developer experience Related to developer experience and/or tools wontfix This will not be worked on
Projects
Milestone

Comments

@calebcartwright
Copy link
Member

calebcartwright commented Dec 28, 2018

I'm leaning towards just for this but still considering cargo-make

@calebcartwright calebcartwright added this to In progress in 1.0 Release Dec 28, 2018
@calebcartwright calebcartwright self-assigned this Dec 28, 2018
@calebcartwright calebcartwright added WIP Work is in progress developer experience Related to developer experience and/or tools labels Dec 28, 2018
@calebcartwright calebcartwright added this to the 1.x Release milestone Dec 28, 2018
@calebcartwright calebcartwright added wontfix This will not be worked on and removed WIP Work is in progress labels Jan 21, 2019
@calebcartwright
Copy link
Member Author

After some thinking/working, I no longer view this as necessary. The vast majority of activities (test, build, run, format, lint, etc.) are all already available directly via a cargo subcommand without requiring any args/options.

The only activity that necessitates a longer command is for code coverage. However, as there are some tooling limitations around code coverage (limited number of tools, with limited OS support, with limited support for stable Rust) I expect this will primarily be a CI activity, and not one run regularly as part of the inner dev loop.

I'd rather add instructions to the Contributing docs for folks developing on Linux that want to generate coverage locally as opposed to introducing something like just or cargo-make solely for running coverage.

Closing this accordingly

1.0 Release automation moved this from In progress to Done Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer experience Related to developer experience and/or tools wontfix This will not be worked on
Projects
1.0 Release
  
Done
Development

No branches or pull requests

1 participant