Skip to content

[improvement][ci] make sure each merge with the chart version promote. #54

@matrixji

Description

@matrixji

Some basic rules needed to add to ci:

  • if things are changed under the charts folder, the version field in charts/devlake/Chart.yaml should be promoted, e.g: v0.14.5 -> v0.14.6, v0.14.5 -> v0.15.0
  • the chart and the devlake version alignment: using the same major and minor version numbers, and could have different patch numbers. e.g chart version v0.14.5 for DevLake version v0.14.2
  • each merge to master should be fast-forwardable and all commits need to squash to one before it merged

I'll add some initial CI actions to check it for PR, and initial some guidance for it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions