Skip to content

Settle on a naming scheme for branches #74

@ageorgou

Description

@ageorgou

So far we have been using a mix: some branches named after the developers, others following a kind of pattern.

Should we have a fixed set of categories, e.g. fix, feature? And what should those be?

Metadata

Metadata

Assignees

No one assigned

    Labels

    technicalRelated to VSCode, packaging etc rather than usage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions