version control - Why does git am leave modified files lying around? How can I adapt my workflow to do better? -
It will be too long, but I hope you can bear with me.
I am trying to use git to keep the source code of my team under version control after trying to find different ways of working for me, finally i
Background:
I have a staging server (mirror output server) that contains all ASPX files. Then I have the init-db < / Em> and created a git repo and git add to track all the files. done
To create a local copy on my laptop, I have actually zipped the ".git" folder to the staging server and FTP has put it on my local machine in "staging.git" To change my development and against it, I did GIT clone staging.git webappfolder .
After committing 2 to feature 1 and feature 2, it's time to implement the change back to the staging server I have done a git format-patch-2 Outputs to 0001blah.patch and 0002blah.patch .
These 2 patch files are then sent to the staging server and I have done the git am 0001blah.patch on the staging server, showing a logging GIT That went through committed but when I do a git status , it displays , but has not been updated: modified: file1.aspx .
What does this mean? I have also tried to apply on git 0001blah.patch but all I had a error "patch was failed: file1.aspx: patch does not apply .
Is there a problem in my workflow? Any information about the proper or helpful information will be very useful. Then, the patching model will be most viable for us now because we will not establish an SSH server at any time.
I just Of Trials:
rm -rf clone? # Clone 1 is copy of work mkdir clone1 (cd clone 1 git init echo foo & gt; file1 git add file1 git commit -m "initial state" ) # Clone 2 Staging Repos GIT Clone Clone 1 Clone 2 # Patch (CD Clone 1 GIT Tag Staging # What is Tag Tagging in the tagging Icho feature1 & gt; file1 git add file1 git commit -m "feature 1" echo feature 2 & Gt; file1 git add file1 git commit -m "feature2" rm * .patch git format-patch taging) #define patches (cd clone 2 git am ../clone1/*.patch # Cygwin / msysgit line Weirdness on the end B Patching cancellation and re-implementing it clears Git am --abort git am ../clone1/*.patch git log git position) minor issue with patches Not done twice without clearly speaking, but with the right content of the end file 1, with a clean drink in Clone 2, nothing looks wrong in your workflow.
Git apply only to update work trees, do not commit.
He said, do not use the GIT repository for staging. My workflow will probably create a release branch / fork of the development repository (or not), and will only deploy its complete clean copies.
For incremental updates in the staging environment, simply use GIT tag staging in the release bracket, email "git diff staging..HEAD> update.patch", and standard unix "patch -P1 "to implement it Should Ary. It is as long as you do not actually need a change history on the staging server.
Comments
Post a Comment