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

Git Branching #27

Open
1 of 3 tasks
Retr0-code opened this issue Nov 8, 2023 · 1 comment
Open
1 of 3 tasks

Git Branching #27

Retr0-code opened this issue Nov 8, 2023 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@Retr0-code
Copy link
Owner

Retr0-code commented Nov 8, 2023

Summary

Use GitFlow in order to develop a new own model of branching.
Please suggest rules in the comments.

Suggestions

  • Add protection rules
  • Decide procedure of pulling requests;
  • Decide branching strategy;

Motivation

Developing a branching strategy will make integration of new code safer and faster.

@Retr0-code Retr0-code added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 8, 2023
@Retr0-code Retr0-code self-assigned this Nov 8, 2023
@Retr0-code
Copy link
Owner Author

To start working developer must create own branch. After that, separate branch should be created for working on a feature or fix. After feature or fix was done, developer must rebase the feature branch to their own branch.

This provides linear commit history in dev's branch and allows to save development progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant