Update publishing, retention and provider verification instructions
This commit is contained in:
1 parent
d5ac22777f
commit
0b53ce880a
1 file changed
+5
-1
@@ -1,7 +1,11 @@
|
||||
- Always bump `VERSION` unless the only changed files are `Dockerfile`, `*.md`, or `VERSION` itself.
|
||||
- Always document code and behavior changes in `CHANGELOG.md` unless the only changed files are `Dockerfile`, `*.md`, or `VERSION` itself.
|
||||
- Update `README.md` whenever user-facing behavior, setup, runtime requirements, Docker usage, or provider state changes.
|
||||
- Commit changes with a clear commit message and push them after verification.
|
||||
- Always commit and push changes with a clear commit message.
|
||||
- when new wersion is published always build a new docker image and push to gitea repo
|
||||
- Preserve data from existing Kaizoku instances. Updates must not wipe `.kaizoku/` state, configuration, queue history, watchlists, thumbnails, downloads, or Jellyfin library content.
|
||||
- When needed, install project tools with `pip` or the platform package manager.
|
||||
- LAN URLs and `github.com` URLs may be accessed when needed for this project.
|
||||
- always check that anime providers are up-to-date so your working with latest code
|
||||
- when solving a errors regarding downloads or searching do a check if the anime providers are up-to-date
|
||||
- always cleanup after new image is pushed, keep only latest and previouse image version delete older
|
||||
Reference in new issue
Block a user