ee7
ee7
Thanks for creating this issue. I agree that the docs could use some updates/improvements. This is a priority on my to-do list for the repo.
I'll keep this as a draft until I make a follow-up PR that adds an append file containing some of the removed details like: > To keep your implementation simple,...
Hi. Thanks for working on this. For background, the current numbers were made relative to the expected end state of the track. That is, I kept everything as "easy" because...
Do not merge as is. I thought I verified that this worked, but on double checking it seems like this PR currently causes release builds to no longer be stripped....
And nit for merging: our PR template has: > - [X] PR title uses [semantic commit messages](https://nitayneeman.com/posts/understanding-semantic-commit-messages-using-git-and-angular/#fix) and that specifies: > The `refactor` type is used to identify development changes...
GitHub [announced on 2024-01-30](https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/): > The macOS 14 runner image is now available for GitHub hosted runners. Workflows executed on this image will run exclusively on the 3 vCPU M1...
Update for 2024-09-03: [GitHub Actions: arm64 Linux runners are now generally available](https://github.blog/changelog/2024-09-03-github-actions-arm64-linux-and-windows-runners-are-now-generally-available/)
Thanks. That does cause `make debug` to pass `--define:debug` to the build command, with the output containing: ```shell docker compose run --rm chalk nimble -y build --define:debug ``` However, `strip`...
CI passed on PR https://github.com/crashappsec/chalk/pull/250, but failed on merging to main: https://github.com/crashappsec/chalk/commit/7cf3029515e283d98525234e8ce849124a1074fc. CI also previously passed on PR https://github.com/crashappsec/chalk/pull/252, but now fails with no changes in the PR.
Also: https://github.com/crashappsec/chalk/blob/66a5bb4b979e9b94f881abf929363db164cba975/chalk.nimble#L15 would probably be better with a commit ref. It's confusing that these are different states: - https://github.com/viega/zippy/releases/tag/v0.10.7 - https://github.com/guzba/zippy/releases/tag/0.10.7