Squashing or editing some commits before doing git-svn dcommit? -
I am working in a Subversion repository with a subject Czech-Paul policy, which includes: each trunk is committed To be reviewed by any other developer and should be mentioned in this committed message.
While working with git-svn I am creating several incremental GIT check-ins which are not reviewed. Their git commit messages reflect this.
What is the best way to use GIT-SVN, but follow the rules of svn repository? Should I just squash all the commissions into a single svn committed? Can I re-write commitments for each amendment with the information under review? Can I "manually" take every personal change to the git master branch and modify the committed message of each before git-svn dcommit?
You can leak your local branch against the subversion tracking branch, which will allow you to squash and modify Offers opportunities.
The next time you dcommit, dcommit will replay your history once and what will be done for this Subversion.
Beliefs:
- The local branch is master
- The master has been examined
- The name of the remote tracking branch is git- Svn is
- git-svn is up to date
What to do:
$ git rebase -i git-svn
will open with a list of comments in your default editor Master to leak against Git-svn you can select, edit, or squash (mix and match if desired ).
After you make your selection, you will be exposed to display a committed message for each commit while writing another temporary file. This is where you amend the committed message.
Alerts:
You are re-writing the history of your repository, be careful while using this behavior until you feel this behavior.
Comments
Post a Comment