Answer the question
In order to leave comments, you need to log in
How to develop together with Github?
It takes two people to work on the same project. My partner has never dealt with git and I have never dealt with teamwork. I have already created a repository on github, I need to give minimal instructions for working together with my partner: simple, without any commands in the console, but through the github for windows client.
I need to write a simple instruction. Tell me if I'm writing correctly and what I'm doing wrong.
I'm creating a branch in which my partner will develop a new feature. This thread is based on the thread I'm working on.
Next is the instruction itself, which needs to be commented. The correct sequence of actions is important.
register here
https://github.com/
press the Fork button here
https://github.com... <repository link>
install the client, enter your login in it
https://windows.github.com/
in the program clone <repository name>
switch to <branch that I created>
write code, commit
then press the pullrequest button. You make a request from <branch I created> to <branch I created>
Next, I press Confirm Merge on GitHub and a new feature developed by a partner appears in my repository.
Question 2
Will the commits that I make in my branches appear in the partner's (copy) repository?
For example, then I need the partner to start developing a new function. I'm creating a branch for this feature based on the branch I was developing at the time the partner wrote the first feature. Will this branch with all my developments appear with a partner?
Where can you find an understandable algorithm, preferably with a video on how to work together in a github. It is important that everything is simple: without any commands in the console and on windows
Answer the question
In order to leave comments, you need to log in
For all interested subscribers spread. I made a file with pictures after viewing which any beginners can start using Git with a remote repository on GitHub
Working through GitHub together without a console and special ...
Understand, GIT is a distributed system. You and your colleague will work in completely different repositories, each with their own. The remote repository will serve as a sync point. So if you make a local brack, only you will have it. That is, in order for this branch to be available to another developer, you must push it to a common remote repository. And here is the fun, since your colleague is working with a fork of the project, you have two remote repositories.
In general, there will be less pain if both of you synchronize changes between each other only through master. Read about git-flow.
It will not work without commands - only the branch on which the HEAD marker stands is unloaded by pull. And constantly using clone is out of the question.
And someday, you will have to merge sources manually, and this is pull - merge - commit - push
Read progit , increase your general level of knowledge.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question