some binary size tests? #678
Conversation
ThouCheese
force-pushed
the
feat/code-size
branch
3 times, most recently
from
656d6e3 to
4358b11
Compare
ThouCheese
force-pushed
the
feat/code-size
branch
from
4358b11 to
a7b477f
Compare
| owner: context.repo.owner, | ||
| repo: context.repo.repo, | ||
| body: comment | ||
| }); |
There was a problem hiding this comment.
I would probably write all this as a Rust tool itself (could be in a separate repo) or as a TypeScript codebase at least — this feels way too fragile, but 🤷 could be a start.
There was a problem hiding this comment.
I’ve seen examples of Rust WASM bindings to the GitHub actions toolkit, alas doesn’t seem to have caught on 😢 I came across this which seems abandoned 6 years ago https://github.com/sethp/actions-toolkit-sys and this from someone at GitHub who likewise seems to have abandoned it https://github.com/peter-evans/rust-wasm-action/tree/master
This ‘octocrab’ crate on the other hand seems maintained and got WASM support last year 👀 (dev sponsored by catppuccin) https://github.com/XAMPPRocky/octocrab
Example use in Apache nuttx (PR review bot) https://lupyuen.org/articles/llm.html#call-the-github-api
ThouCheese
force-pushed
the
feat/code-size
branch
2 times, most recently
from
d4cf406 to
2cca0c7
Compare
ThouCheese
force-pushed
the
feat/code-size
branch
from
2cca0c7 to
bb06045
Compare
|
Are we okay closing this now that cargo-bloat & cargo-llvm-lines are ran in CI and reported as a comment? |
No description provided.