|
210 | 210 | "\n", |
211 | 211 | " ```shell\n", |
212 | 212 | " git fetch -t\n", |
| 213 | + " git checkout develop-white\n", |
| 214 | + " git checkout develop-black\n", |
213 | 215 | " ```\n", |
214 | 216 | " \n", |
215 | 217 | "2. Switch to your feature branch and merge `develop-white` (in order to get the latest changes in `develop` before switching to `black`):\n", |
216 | 218 | "\n", |
217 | 219 | " ```shell\n", |
218 | 220 | " git checkout YOUR_BRANCH\n", |
219 | 221 | " git pull\n", |
| 222 | + " pre-commit uninstall || pip install pre-commit\n", |
220 | 223 | " git merge --no-ff develop-white\n", |
221 | 224 | " ```\n", |
222 | 225 | " If merge conflicts arise, resolve them and conclude the merge as instructed by Git.\n", |
|
241 | 244 | " ```shell\n", |
242 | 245 | " git merge --no-ff develop-black\n", |
243 | 246 | " ```\n", |
244 | | - " * If merge conflicts arise, resolve them and conclude the merge as instructed by Git.\n", |
245 | | - " Most conflicts will probably be resolved by choosing \"Ours\" over \"Theirs\" or the \"Current Change\" over the \"Incoming Change\".\n", |
246 | | - " Still, be careful!\n", |
247 | | - " * Once all conflicts are resolved, check if the tests pass.\n", |
248 | | - " If so, the formatting was successful.\n", |
249 | | - " If you cannot import Climada, one of the merges inflicted erroneous syntax.\n", |
250 | | - " You will have to fix this manually before you commit the merge.\n", |
| 247 | + " Resolve all conflicts by choosing \"Ours\" over \"Theirs\" (\"Current Change\" over the \"Incoming Change\").\n", |
| 248 | + " \n", |
| 249 | + " ```shell\n", |
| 250 | + " git checkout --ours .\n", |
| 251 | + " git add -u\n", |
| 252 | + " git commit\n", |
| 253 | + " ```\n", |
251 | 254 | " \n", |
252 | 255 | "6. Now, get up to date with the latest `develop` branch:\n", |
253 | 256 | "\n", |
|
258 | 261 | " git merge --no-ff develop\n", |
259 | 262 | " ```\n", |
260 | 263 | " Again, fix merge conflicts if they arise and check if the tests pass.\n", |
| 264 | + " Accept the incoming changes for the tutorials 1_main, Exposures, LitPop Impact, Forecast and TropicalCyclone unless you made changes to those.\n", |
| 265 | + " Again, the file with the most likely merging conflicts is CHANGELOG.md, which should probably be resolved by accepting both changes.\n", |
| 266 | + " \n", |
261 | 267 | " \n", |
262 | 268 | "7. Finally, push your latest changes:\n", |
263 | 269 | "\n", |
|
0 commit comments