ci: Audit and correct CI jobs to work on forks - #1202
Conversation
9bda1f1 to
cdebc25
Compare
cdebc25 to
0697bf3
Compare
0697bf3 to
fb8288f
Compare
Python Scan Results (requirements.txt)Scan Date: 2026-07-29T10:15:19.856307612Z Nothing Found |
Python Scan Results (requirements_production.txt)Scan Date: 2026-07-29T10:15:27.143494509Z Nothing Found |
Python Scan Results (requirements_docker.txt)Scan Date: 2026-07-29T10:15:21.551226547Z Nothing Found |
Python Scan Results (requirements_dev.txt)Scan Date: 2026-07-29T10:15:23.784467761Z Nothing Found |
Image Scan ResultsScan Date: 2026-07-29T10:30:37.498325861Z Nothing Found |
|
testing docker logic changes: nofusscomputing/action_docker@c7acc65 Techniqally passed, however since logic was corrected vuln scanning was not passed |
442f3f6 to
6cfcc44
Compare
6cfcc44 to
4b13c91
Compare
|
testing docker logic changes:
Job: |
report should only fail if the report is empty ref: nofusscomputing/centurion_erp#1202 nofusscomputing/centurion_erp#1201
|
testing docker python upgrades: let jobs complete fully this time, unless bugs out
Job: |
… changed. must always run on master, development and feat-next-release ref: nofusscomputing/centurion_erp#1202 nofusscomputing/centurion_erp#1201
|
testing docker python upgrades: let jobs complete fully this time, unless bugs out
Job:
🏁 On Success Merge |
… changed. must always run on master, development and feat-next-release ref: nofusscomputing/centurion_erp#1202 nofusscomputing/centurion_erp#1201
GH does not have feature where you can make requirement skip if not exists ref: nofusscomputing/centurion_erp#1202 nofusscomputing/centurion_erp#1201
📚 Summary
Closes: Audit and correct CI jobs so they work on repo forks #1201
Related: fix(access): Give the entity Base serializers unique schema component names #1199
🔗 Links / References
👷 Tasks
🔍 Code Reviewer 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