chore: restringir gatilho de geracao de imagem apenas a pasta src - #13
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 946ce6e42a
ℹ️ 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.
When a commit to master changes only Dockerfile, pyproject.toml, or .dockerignore, this filter now skips the entire release workflow, leaving the published latest image stale. These are direct Docker build inputs—Dockerfile copies pyproject.toml and installs the package—so changes to the base image, runtime configuration, dependencies, packaging metadata, or build context will not reach GHCR until an unrelated src/** change or tag push occurs. Keep these paths in the trigger, or separate image publication from any workflow work that should be limited to source changes.
Useful? React with 👍 / 👎.
1 participant
Configura o release.yml para que somente alteracoes na pasta src acionem a publicacao de novas imagens no GitHub Packages.