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.

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

[Suggestion] - Branching the git #20

Closed
Nejcc opened this issue May 27, 2021 · 1 comment
Closed

[Suggestion] - Branching the git #20

Nejcc opened this issue May 27, 2021 · 1 comment

Comments

@Nejcc
Copy link

Nejcc commented May 27, 2021

Strongly suggest start branching the git workflow for your very nice project.

  • Master (release / pre-release) (lock master branch )
    • Stag (copy of production / pass all tests before marge to master )
    • Develop (Main develop branch)
      • Features/*
      • Bugs/*
      • Theme/*
      • Security/*

:)

@eporsche
Copy link
Owner

eporsche commented Jun 1, 2021

Currently, it is not required to add more complexity to the git flow, since there is no "active" 5+ dev community working on the project. Moreover, at this stage, the project is in the pre-release phase.

@eporsche eporsche closed this as completed Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants