Description
Developers have to remember multiple cargo commands for building, testing, formatting, and deploying. A Makefile with well-named targets makes the development workflow much more ergonomic.
Requirements and context
make build — build optimised WASM
make test — run full test suite
make fmt — format code
make lint — run clippy
make deploy-testnet — deploy to testnet
make coverage — run tarpaulin coverage
- Document all targets in Makefile with comments
Suggested execution
git checkout -b chore/makefile
- Create
Makefile at repo root
- Write all targets
- Test each on a clean checkout
- Document in README
Example commit message
chore: add Makefile with common developer workflow targets
Description
Developers have to remember multiple cargo commands for building, testing, formatting, and deploying. A Makefile with well-named targets makes the development workflow much more ergonomic.
Requirements and context
make build— build optimised WASMmake test— run full test suitemake fmt— format codemake lint— run clippymake deploy-testnet— deploy to testnetmake coverage— run tarpaulin coverageSuggested execution
Makefileat repo rootExample commit message
chore: add Makefile with common developer workflow targets