Skip to content

Commit cb0a0d4

Browse files
committed
docs: add "Updating Your Branch"
1 parent 58aa05e commit cb0a0d4

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

contributing/workflow.md

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,6 @@ that it could benefit from a review by fellow developers.
155155
> Remember to sync your local repo with the shared one before pushing!
156156
It is a lot easier to resolve conflicts at this stage.
157157

158-
159158
Synchronize your repository:
160159

161160
git checkout develop
@@ -215,6 +214,33 @@ Label your PRs with the one of the following [labels](https://github.com/codeign
215214
And if your PRs have the breaking changes, label the following label:
216215
- **breaking change** ... PRs that may break existing functionalities
217216

217+
## Updating Your Branch
218+
219+
If you are asked for changes in the review, commit the fix in your branch and push it to GitHub again.
220+
221+
If the `develop` branch progresses and conflicts arise that prevent merging, or if you are asked to *rebase*,
222+
do the following:
223+
224+
Synchronize your repository:
225+
226+
git checkout develop
227+
git fetch upstream
228+
git merge upstream/develop
229+
git push origin develop
230+
231+
Bring your feature branch up to date:
232+
233+
git checkout new/mind-reader
234+
git rebase upstream/develop
235+
236+
You might get conflicts when you rebase. It is your
237+
responsibility to resolve those locally, so that you can continue
238+
collaborating with the shared repository.
239+
240+
And finally push your local branch to your GitHub repository:
241+
242+
git push --force-with-lease origin new/mind-reader
243+
218244
## Cleanup
219245

220246
If your PR is accepted and merged into the shared repository, you can

0 commit comments

Comments
 (0)