Skip to content

Commit

Permalink
Add screenshot for PR with comflicts
Browse files Browse the repository at this point in the history
  • Loading branch information
tverbeiren committed Feb 20, 2024
1 parent 14dcdbf commit 734b60d
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/use-github.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -192,12 +192,16 @@ Now that the changes are pushed/synced with the PR, this update is picked up aut

When the updates in the PR are rendered properly and they are satisfactory, we can take a step further and update the `develop` branch. This can be done in the PR window. In most cases the bottom of the PR page will look something like this:

~[](img/gh-pr_merge_1.png){width=50%}
![](img/gh-pr_merge_1.png){width=70%}

And updating `develop` is as simple as pressing the button 'Merge pull request'.

It may occur that there is a merge conflict, for instance when someone else has already updated the `develop` branch and so prior information would be overwritten. This case can sometimes be resolved easily but usually requires one to manually resolve the merge conflicts.

The following indicates that conflicts occur:

![](img/gh-pr_conflict.png){width=70%}

## Merge with `main`

When the merge with `develop` is done we can check if our changes are correct once more. Please note that we need this step because multiple people might have updated multiple parts of the app in their own branch and merged this with `develop`. We have to change if those changes are compatible and make sense.
Expand Down

0 comments on commit 734b60d

Please sign in to comment.