Skip to content

Commit e4c034b

Browse files
committed
Add troubleshooting steps for local setup issues
1 parent 6a4eb12 commit e4c034b

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

CONTRIBUTING.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,7 @@
5656
- [Roadmap](#roadmap)
5757
- [Versions](#versions)
5858
- [Releasing Gitea](#releasing-gitea)
59+
- [Troubleshooting Issues](#troubleshooting-issues)
5960

6061
</details>
6162

@@ -604,3 +605,27 @@ be reviewed by two maintainers and must pass the automatic tests.
604605
- bump the version of https://dl.gitea.com/gitea/version.json
605606
- merge the blog post PR
606607
- announce the release in discord `#announcements`
608+
609+
Here's the README content based on the screenshot, excluding the second step:
610+
611+
---
612+
613+
## Troubleshooting Issues
614+
615+
If you encounter errors during the local setup after forking the repository, such as issues with cloning or missing dependencies, here are the steps to resolve them:
616+
617+
- **Issue:** Cloning fails with errors like `curl error: RPC failed` or `HTTP/2 stream was not closed cleanly`.
618+
619+
- **Solution:**
620+
1. Increase the HTTP buffer size:
621+
```sh
622+
git config --global http.postBuffer 524288000
623+
```
624+
2. To reduce the size of data fetched during the initial clone, you can use:
625+
```sh
626+
git clone --depth 1 https://github.com/<username>/gitea.git
627+
```
628+
629+
You can replace `username/repo` with the appropriate repository information before using this content.
630+
631+
---

0 commit comments

Comments
 (0)