Cloning upstream repository
For any project that has no Git repository, add a widget for the project lead to create one by entering the URL of an upstream source tree.
Sponsor This Project
Sponsor This Project
You currently need to log in to sponsor a project. We apologize for the inconvenience.
Note: You can propose changes using the forum below.
For any project that has no Git repository, add a widget for the project lead to create one by entering the URL of an upstream source tree.
Supported upstream source URL types should include SVN, Git and tarballs or ZIP files via HTTP or FTP.
For supported source types (Git, SVN) the repository is periodically updated from the upstream source. This should be an automatic process unless there are conflicts which prevent this, the handling of these conflicts is unspecified. It is recommended that repositories of this type have all changes committed to the upstream source to avoid such conflicts.
For tarballs and ZIP files the project lead is able to manually update the repository by providing another file. This changes are stored as a single commit in the repository.
Supported upstream source URL types should include SVN, Git and tarballs or ZIP files via HTTP or FTP.
For supported source types (Git, SVN) the repository is periodically updated from the upstream source. This should be an automatic process unless there are conflicts which prevent this, the handling of these conflicts is unspecified. It is recommended that repositories of this type have all changes committed to the upstream source to avoid such conflicts.
For tarballs and ZIP files the project lead is able to manually update the repository by providing another file. This changes are stored as a single commit in the repository.
Change History:
- 2012-10-01 10:37 EDT [ACCEPTED] Specify that updates are handled
