Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[capella-dev] Easy contribution on Github

Hi,

 

We have a “quite simple process” for contributions:

 

 

If you clone locally the repository, you have seen that there is many branches:

 

This can be filtered by fetching only several branches:

 

 

You can retrieve only v* branches (v1.3.x 1.4.x..) and master. (not all other ones)

 

 

 

 

For non commiters:

 

Additionally, for non commiters, as you have to fork the repository, then you have to keep your repository synchronized with the eclipse one, which can be complicated to follow.



By adding both remotes on your clone, you can see if your fork is synchronized with the eclipse one.

 

Here, I have added both repositories, eclipse and my fork, my master branch is not up-to-date with the eclipse/capella one.

 

               

 

One way would be to push the eclipse/master to pdulth/master, then it will be synchronized again.

 

               

 

 

Another way is to delete pdulth/master or to (avoid to fetch it)

 

 

For your fork:

 

 

You will fetch only all your branch starting with pdu- from the fork.

 

For Eclipse, you can retrieve only v* branches (v1.3.x 1.4.x..) and master. (not all other ones)

 

 

               

 

By fetching both remote, you will have only:

 

 

 

----

 

Now, to start a new work, just :

 

-          create from eclipse/master a local branch,

 

-          do your job

-          push a branch to your fork : pdu-bugfix-0101050 for instance,

-          and do a pull request towards eclipse/master.

-          Once merged, just fetch eclipse remote and start again.

 

 

Philippe


Back to the top