Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JDT Core git tips"
(New page: This page should summarize all tips used by the JDT/Core team to get used to git.) |
|||
| Line 1: | Line 1: | ||
This page should summarize all tips used by the JDT/Core team to get used to git. | This page should summarize all tips used by the JDT/Core team to get used to git. | ||
| + | |||
| + | ;buildnotes:in the old workflow I created a patch without updating the build notes, and made that change just before committing | ||
| + | :* with git creating a patch requires to commit first, so either | ||
| + | :** we always create patches which include the change to the buildnotes, or | ||
| + | :** we have to amend a commit just for the buildnotes into the main commit just before pushing to upstream. | ||
Latest revision as of 11:31, 27 September 2011
This page should summarize all tips used by the JDT/Core team to get used to git.
- buildnotes
- in the old workflow I created a patch without updating the build notes, and made that change just before committing
- with git creating a patch requires to commit first, so either
- we always create patches which include the change to the buildnotes, or
- we have to amend a commit just for the buildnotes into the main commit just before pushing to upstream.
- with git creating a patch requires to commit first, so either