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 #3

Closed
2 of 7 tasks
atherdon opened this issue Mar 15, 2018 · 1 comment
Closed
2 of 7 tasks

git #3

atherdon opened this issue Mar 15, 2018 · 1 comment
Assignees

Comments

@atherdon
Copy link
Contributor

atherdon commented Mar 15, 2018

Description/Steps to reproduce

  • convert our flow to good git-flow.
  • broke few forks(0)
  • make 30 commits (15)
  • make 9 pull requests (4)
  • make 6 merge conflicts and fix them (1)
  • make 5-10 future branches, related in a different ways(few times checkout from develop, few times from each other feature branch)(6)
  • 6 branch merges(4)

use command line only

https://github.com/blog/831-issues-2-0-the-next-generation
https://stackoverflow.com/questions/1687262/link-to-the-issue-number-on-github-within-a-commit-message
https://guides.github.com/features/issues/

https://stackoverflow.com/questions/4528869/how-do-you-attach-a-new-pull-request-to-an-existing-issue-on-github

Expected result

Additional information

@khyati0212
Copy link
Collaborator

I will do pull and merge once I make some changes. Right now could not think of any changes.

khyati0212 pushed a commit that referenced this issue Apr 9, 2018
….17.3

Bump nodemon from 1.17.2 to 1.17.3
khyati0212 added a commit that referenced this issue Apr 9, 2018
made changes for creating pull request. For issue #7 #3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants