936
edits
User:Callahanp: Difference between revisions
Jump to navigation
Jump to search
→Part 1B - Create Sourceforge Forks for each Flightgear git repository you need to work in
| Line 53: | Line 53: | ||
===== Part 1B - Create Sourceforge Forks for each Flightgear git repository you need to work in ===== | ===== Part 1B - Create Sourceforge Forks for each Flightgear git repository you need to work in ===== | ||
If you are not going to make changes to a particular repository, but only wish to | If you are not going to make changes to a particular repository, but only wish to do builds tracking next, you only need a clone of the official Flightgear on your local machine. You don't need to bother with creating a SourceForge Fork. You can have a mixture of local gits, some with multiple remote connections origin, upstream and possibly others, others only connected once to flightgear as origin. | ||
Note that if you later decide to contribute to a new area, you will be able to create a fork and attach it to the local clone you previously created using the steps below. | In order not to strain SourceForge resources, it's a good Idea to get rid of any forks that are not used for a while, certainly any that are not used at all for changes and experimental branches. This is especially true of resources that are large. | ||
Note that if you later decide to contribute to a new area, or to resume contributing, you will be able to create a fork and attach it to the local clone you previously created using the steps below. | |||
* Open https://sourceforge.net/projects/flightgear/ | * Open https://sourceforge.net/projects/flightgear/ | ||
| Line 63: | Line 65: | ||
If you don't see Git under personal tools in your profile page, it's because you've not set up any SourceForge Forks yet. | If you don't see Git under personal tools in your profile page, it's because you've not set up any SourceForge Forks yet. | ||
Creating a Sourceforge fork is easy, Just go to the FlightGear Repo you wish to fork and click the fork button on the Left. It takes a few minutes and is pretty easy to figure out. You'll get to see the clone statement for the repo after refreshing the page after the fork is created. | |||
===== Part 2 - Create a local clone for each Sourceforge Fork ===== | |||
If you already have clones of Flightgear git repos from Sourceforge, there's no need to re-do them as clones of your SourceForge Forks, they can easily be converted using the same steps you would use on a fresh clone of a personal fork. | |||
** create origin remote | ** create origin remote | ||
** create upstream remote | ** create upstream remote | ||