Skip to content

Minimize Docker image release frequency #264

@CasperWA

Description

@CasperWA

I suggest to only release new Docker images if the actual necessary files are altered.
For example, if a dependency update PR is merged that only touches development-necessary files (like updating the development requirements), then a new Docker image shouldn't be released. At least not if the update doesn't have any implications on the core files.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CI/CDContinuous integration (CI) & continuous deployment (CD)dockerDocker-related issue or PR

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions