Download the PHP package phillipsdata/git-migrate without Composer
On this page you can find all versions of the php package phillipsdata/git-migrate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download phillipsdata/git-migrate
More information about phillipsdata/git-migrate
Files in phillipsdata/git-migrate
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package git-migrate
Git Migrate
A utility for migrating from SVN to Git.
Uses Atlassian's svn-migration-scripts to migrate various SVN repositories to Git. This utility is particularly useful when you have many externals grouped under a single SVN URL.
How it Works
- GitMigrate will execute
giton your machine to clone an SVN repository to a local path. Note: Your repositories MUST be in standard SVN format (/trunk, /branches, /tags). - GitMigrate will then execute the svn-migration-scripts to place tags in their correct location.
Usage
0. Install git on your machine
If you don't already have git installed, install it.
Then make sure it can be executed via git.
You'll also need to ensure you have a somewhat modern version of java as well.
1. Install via composer
2. Create your config
The config is a JSON file that represents the repositories that you wish to operate on,
as well as any other options that are available as parameters to the git-migrate utility.
It looks like this:
Each repository's path is a URI of the url option specified.
Notice how our repo2 has no origin. The origin is optional for all repositories.
Setting an origin allows us to push the repository to that remote repository using the --push flag.
See the Options section for an explanation of the various other options.
Items File (deprecated)
The items config is a file that returns the directory structure of individual repositories. If you're simply migrating a single repository that might look like:
If, on the other hand, you're migrating a bunch of externals into their own separate git repos (which is probably why you're using this), your config would be structured more like:
This method is deprecated in favor of specifying the repositories using the JSON config file described above.
3. Run the migration
This will create a Git repository from your SVN repository, cloning your trunk, branches, and tags.
Keep in mind that if you're migrating externals that exist in some sub-directory you'll need to adjust the url accordingly. I suggest running the migration for your main repository separately from your externals.
4. Keeping it in sync
While you're making the transition from SVN to Git, you'll only be able to make
commits to your SVN repository, so you'll need some way to keep the repositories
in sync. You can do this by appending the --sync flag.
5. Pushing to a remote origin
The final step in migrating to Git is sharing your repository. You do this by
pushing it to a remote repository with the --push flag (be sure you've defined
the origin for each repository in your config you wish to push).
Options
- config The JSON file to use for setting the configurable options.
- items The path to your items config (deprecated, use config).
- dir The full system path where the Git repositories should be created.
- authors The full system path to the authors file. See Atlassian's migration guide.
- url The URL to your Subversion repository.
- javalib The full system path to Atlassian's svn-migration-scripts.jar file.
- clone Set if you want to clone the Subversion repositories into Git repositories (default).
- sync Set if you need to update the existing Git repositories with commits from their Subversion repository.
- push Set if you want to push the existing Git repositories to their remote origins.
