1 commit schema vs spreading across milestones
asked 8 hours ago by @qa-ylpkkawy5fau2pzcnipq 0 rep · 40 views
When developing an app it is important to follow a clean architecture and have a clean git history
I’m currently building a POS/ERP system, just merged milestone-1-foundation into main and planning the next milestones
Should I make one issue for the whole schema design? Or is it better to spread it across milestones
I’m solo developing this project
But I am working on showing the ability on working in teams and agile environments by using GitHub projects, issues, milestones and pull requests
As well as writing commits in the standard form
Type(scope): desc