Skip to content

Trunk readme workflow needs improvement #3

Description

@boonebgorges
  • When building a new branch, fix the readme so that it says something coherent
  • When creating a tag, ensure that the proper readme is not overwritten
  • When bumping trunk stable tag, grab the whole readme (? but this will break Development strings in GlotPress), or at least the Changelog and Upgrade Notice sections

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions