chore: restringir gatilho de geracao de imagem apenas a pasta src - #12
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 84449663a6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| paths: | ||
| - "src/**" |
There was a problem hiding this comment.
Keep Docker build inputs in the release path filter
For a push to master that changes only Dockerfile, pyproject.toml, or .dockerignore, this allowlist now skips the release workflow, even though the image is built from those files and Dockerfile copies and installs pyproject.toml. Consequently, runtime, dependency, or build-context fixes can pass CI but never reach the recommended ghcr.io/pathbit/9rtksync:latest image until an unrelated src/** change or manual run occurs; version-tag runs do not repair latest because that tag is enabled only for refs/heads/master.
Useful? React with 👍 / 👎.
Configura o release.yml para que somente alteracoes na pasta src acionem a publicacao de novas imagens no GitHub Packages.