{"action":"created","issue":{"url":"https://api.github.com/repos/composer/composer/issues/4293","labels_url":"https://api.github.com/repos/composer/composer/issues/4293/labels{/name}","comments_url":"https://api.github.com/repos/composer/composer/issues/4293/comments","events_url":"https://api.github.com/repos/composer/composer/issues/4293/events","html_url":"https://github.com/composer/composer/issues/4293","id":97068455,"number":4293,"title":"Revision file for create-project command","user":{"login":"ro0NL","id":1047696,"avatar_url":"https://avatars.githubusercontent.com/u/1047696?v=3","gravatar_id":"","url":"https://api.github.com/users/ro0NL","html_url":"https://github.com/ro0NL","followers_url":"https://api.github.com/users/ro0NL/followers","following_url":"https://api.github.com/users/ro0NL/following{/other_user}","gists_url":"https://api.github.com/users/ro0NL/gists{/gist_id}","starred_url":"https://api.github.com/users/ro0NL/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ro0NL/subscriptions","organizations_url":"https://api.github.com/users/ro0NL/orgs","repos_url":"https://api.github.com/users/ro0NL/repos","events_url":"https://api.github.com/users/ro0NL/events{/privacy}","received_events_url":"https://api.github.com/users/ro0NL/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/composer/composer/labels/Support","name":"Support","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":21,"created_at":"2015-07-24T14:44:00Z","updated_at":"2015-07-27T17:42:14Z","closed_at":null,"body":"Hi,\r\n\r\nWe currently use the `create-project` command to create new projects based on our template project. Before we forked the template project.\r\n\r\nWe are testing some update processes, i.e. keep the project in sync with the template project. With forking this was easy.. as we can add the forked remote to our project (`git checkout origin/master && git merge template/master`). However history-wise this was not ideal so we switched to `create-project`.\r\n\r\nThe update process using `create-project` should be done using a patch file with all changes from the revision when the project was created to the latest revision.\r\n\r\nWe currently create a TEMPLATE_REVISION file manually which references the commit hash from our template project, so we later can create a patch file with all later changes.\r\n\r\nI would be nice if this revision file was touched automatically by composer.. any thoughts? Perhaps the whole process of creating/applying the patch file (i.e. updating) could be done by composer... :|\r\n\r\n`composer update-project`"},"comment":{"url":"https://api.github.com/repos/composer/composer/issues/comments/125283742","html_url":"https://github.com/composer/composer/issues/4293#issuecomment-125283742","issue_url":"https://api.github.com/repos/composer/composer/issues/4293","id":125283742,"user":{"login":"mediamonks-robert","id":7644785,"avatar_url":"https://avatars.githubusercontent.com/u/7644785?v=3","gravatar_id":"","url":"https://api.github.com/users/mediamonks-robert","html_url":"https://github.com/mediamonks-robert","followers_url":"https://api.github.com/users/mediamonks-robert/followers","following_url":"https://api.github.com/users/mediamonks-robert/following{/other_user}","gists_url":"https://api.github.com/users/mediamonks-robert/gists{/gist_id}","starred_url":"https://api.github.com/users/mediamonks-robert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mediamonks-robert/subscriptions","organizations_url":"https://api.github.com/users/mediamonks-robert/orgs","repos_url":"https://api.github.com/users/mediamonks-robert/repos","events_url":"https://api.github.com/users/mediamonks-robert/events{/privacy}","received_events_url":"https://api.github.com/users/mediamonks-robert/received_events","type":"User","site_admin":false},"created_at":"2015-07-27T17:42:14Z","updated_at":"2015-07-27T17:42:14Z","body":"That's the difference with my use case, I want to start clean because the project I create has it's own repository, I'm not interested in pushing back changes. It would be really nice to have the revision of that version so in case of one way patches from the template project to the actual project.\r\n\r\nWill do some digging in Composer source to see if I can find an easy fix to get the vcs revision in root package object as getFullPrettyVersion() only returns \"dev-develop\" instead of \"dev-develop <hash>\"."}}