-
Notifications
You must be signed in to change notification settings - Fork 2
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
read about git flow and create a future branch for development process #7
Comments
created new "futureBranch" haven't changed the code so could not generate pull request. |
@khyati0212 you can add some changes at readme file in order to have a practice |
khyati0212
added a commit
that referenced
this issue
Apr 9, 2018
Done. Did some changes into readme file. Worked on futureBranch. Created pull request. |
can you create another branch, named develop from futureBranch? |
Done. Created new branch develop from futureBranch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description/Steps to reproduce
https://codeburst.io/trunk-based-development-vs-git-flow-a0212a6cae64 i'll examine you. understand the logic of future branching.
https://devcenter.heroku.com/articles/node-best-practices
The text was updated successfully, but these errors were encountered: