Original Post: Using Bento individually and on team projects
Bento 0.8 has been designed to be more user-friendly for individual use rather than requiring team-wide adoption. This release addresses feedback about its file footprint and the modification of Git states. Key changes include:
- Individual contributors will not affect others’ workflows with Bento files.
- Bento automatically checks code as you commit, focusing only on changed files.
- Initial setup no longer reveals a project’s entire tech debt.
For personal use, Bento checks code at commit and can be run manually with commands like bento check and bento check --all. The autorun feature can block commits if issues are found, but this can be disabled.
To use Bento for team collaboration, configurations should be added to Git, and contributors can initialize Bento using the project setup. Configuration files have been moved to a global folder ~/.bento/, reducing the project’s footprint.
For CI/CD integration, Bento can analyze the entire project and use its archive feature to ignore existing issues, focusing only on new ones. The setup involves installing Bento in the CI environment and running appropriate commands.
Feedback is welcomed through email, Slack, or GitHub issues.
Go here to read the Original Post