Skip to content

Commit 2d94374

Browse files
kopporsubhramit
andauthored
Add FAQ on upstream sync (#13238)
Co-authored-by: Subhramit Basu <subhramit.bb@live.in>
1 parent b2104a1 commit 2d94374

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/code-howtos/faq.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,17 @@ Following is a list of common errors encountered by developers which lead to fai
1010
* Sync your fork with the JabRef repository: [General howto by GitHub](https://help.github.com/articles/syncing-a-fork/)
1111
* Branches and pull requests (🇩🇪): [https://github.com/unibas-marcelluethi/software-engineering/blob/master/docs/week2/exercises/practical-exercises.md](https://github.com/unibas-marcelluethi/software-engineering/blob/master/docs/week2/exercises/practical-exercises.md)
1212

13+
## Failing GitHub workflow "Sync fork with upstream"
14+
15+
To ease development, a GitHub workflow automatically updates your `main` branch daily.
16+
However, it is not allowed to update your files if the GitHub workflows are updated by the JabRef team.
17+
Therefore, GitHub notifies you now and then that "Sync fork with upstream failed for main branch".
18+
19+
To solve this issue, open your GitHub repository in your browser.
20+
Then, click "Sync fork" to get your fork up-to-date and get the workflow passing again.
21+
22+
![Sync fork](https://github.com/user-attachments/assets/5c1b0a17-0fde-4ce8-ac46-d9477a65c345)
23+
1324
## Failing tests
1425

1526
### Failing <b>Checkstyle</b> tests

0 commit comments

Comments
 (0)