Use Forgejo workflows and registry
All checks were successful
publish-latest / docker (push) Successful in 9s
ci / test (3.10) (push) Successful in 19s
ci / test (3.12) (push) Successful in 19s
ci / test (3.13) (push) Successful in 19s
ci / container (push) Successful in 7s
publish-image / docker (push) Successful in 8s
All checks were successful
publish-latest / docker (push) Successful in 9s
ci / test (3.10) (push) Successful in 19s
ci / test (3.12) (push) Successful in 19s
ci / test (3.13) (push) Successful in 19s
ci / container (push) Successful in 7s
publish-image / docker (push) Successful in 8s
This commit is contained in:
parent
dbc7464b58
commit
e7bde2b3f4
12 changed files with 134 additions and 40 deletions
18
.forgejo/pull_request_template.md
Normal file
18
.forgejo/pull_request_template.md
Normal file
|
|
@ -0,0 +1,18 @@
|
|||
## Summary
|
||||
|
||||
Describe the problem and the focused solution.
|
||||
|
||||
## Verification
|
||||
|
||||
- [ ] `python -m py_compile wlc_monitor.py`
|
||||
- [ ] `python -m unittest discover -v`
|
||||
- [ ] `python -m pip check`
|
||||
- [ ] Docker checks run, or not applicable
|
||||
- [ ] User-facing documentation updated, or not applicable
|
||||
- [ ] No credentials, private infrastructure data, runtime state, or personal data
|
||||
are present in the diff
|
||||
|
||||
## Operational impact
|
||||
|
||||
Call out compatibility, configuration, alerting, state-migration, or deployment
|
||||
effects.
|
||||
Loading…
Add table
Add a link
Reference in a new issue