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.

Sign up for GitHub

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

Jump to bottom

Bot tracking binary size #39

Open
benbrittain opened this issue Jul 10, 2020 · 0 comments
Open

Bot tracking binary size #39

benbrittain opened this issue Jul 10, 2020 · 0 comments
Labels
discussion Active proposal enhancement New feature or request help wanted Extra attention is needed

Comments

@benbrittain
Copy link
Contributor

There are some changes to the library (as well as increasing usage!) and I'd like to prevent size regressions. We should check binary output on a slew of targets/configs on every commit
@benbrittain benbrittain added discussion Active proposal enhancement New feature or request help wanted Extra attention is needed labels Jul 10, 2020
@benbrittain benbrittain mentioned this issue Jul 11, 2020
Open
blt pushed a commit to blt/argh that referenced this issue Aug 17, 2020
Introduce 'cargo bloat' action step
761d322 
This commit introduces the [cargo-bloat](https://github.com/marketplace/actions/cargo-bloat)
step into the `Argh` action. The purpose of bloat is to observe the size of produced artifacts
over time and report on PRs etc how the size is changing.

Resolves google#39
@blt blt mentioned this issue Aug 17, 2020
Closed
blt pushed a commit to blt/argh that referenced this issue Aug 17, 2020
Introduce 'cargo bloat' action step
c4e022b 
This commit introduces the [cargo-bloat](https://github.com/marketplace/actions/cargo-bloat)
step into the `Argh` action. The purpose of bloat is to observe the size of produced artifacts
over time and report on PRs etc how the size is changing.

Resolves google#39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion Active proposal enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduce 'cargo bloat' action step blt/argh
1 participant
@benbrittain