Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Settle on a naming scheme for branches #74

Open
ageorgou opened this issue Oct 12, 2021 · 1 comment
Open

Settle on a naming scheme for branches #74

ageorgou opened this issue Oct 12, 2021 · 1 comment
Labels
technical Related to VSCode, packaging etc rather than usage

Comments

@ageorgou
Copy link
Contributor

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?
@ageorgou ageorgou added the technical Related to VSCode, packaging etc rather than usage label Oct 12, 2021
@raquelalegre
Copy link
Contributor

What I'm using in other projects is:

  • feature for addition of new functionality
  • fix for bug fixing
  • docs when working on user/developer documentation
  • release for new releases
  • test when writing tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
technical Related to VSCode, packaging etc rather than usage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ageorgou @raquelalegre