chore: Hit the ground running development - #1200
Conversation
a3dc369 to
5e0172c
Compare
Image Scan ResultsScan Date: 2026-07-28T11:49:19.178183985Z Nothing Found |
Python Scan Results (requirements_dev.txt)Scan Date: 2026-07-28T11:34:27.69850212Z Nothing Found |
Python Scan Results (requirements_docker.txt)Scan Date: 2026-07-28T11:34:21.117663111Z Nothing Found |
Python Scan Results (requirements.txt)Scan Date: 2026-07-28T11:34:31.468068773Z Nothing Found |
Python Scan Results (requirements_production.txt)Scan Date: 2026-07-28T11:34:37.400292285Z Nothing Found |
a194e60 to
12dec13
Compare
12dec13 to
37b59e9
Compare
37b59e9 to
a776cd7
Compare
|
@louzolo123 Do you mind taking a look at this as someone whom just began this workflow. Have i covered what was initially missing? feel free to add review comments. |
Yes, I think you covered everything that was initially missing. The workflow looks good to me. Great job! I'll leave review comments if needed. |
📚 Summary
The purpose of this PR is to make changes that enable a developer to go from
blank dev machinetosetup and ready to developin such a way that is simple and easy to follow.Scope for this PR is as follows:
🔗 Links / References
👷 Tasks
Feature Release ONLY 🟥 Squash migration files 🟥
Multiple migration files created as part of this release are to be sqauashed into a few files as possible so as to limit the number of migrations
🧨 Contains breaking-change Any Breaking change(s)?
Breaking Change must also be notated in the commit that introduces it and in Conventional Commit Format.
📘 Documentation written
All features to be documented within the correct section(s). Administration, Development and/or User
🏁 Milestone assigned
⚙️ 🧪 Functional Test(s) Written
🧪 Unit Test(s) Written
ensure test coverage delta is not less than zero
📄 Roadmap updated