* 📑 update mkdocs * rename docker override file and add to gitignore * update .env.example - GOOGLE_MODELS * update index.md * doc refactor: split installation and configuration in two sub-folders * doc update: installation guides * doc update: configuration guides * doc: new docker override guide * doc: new beginner's guide for contributions - Thanks @Berry-13 * doc: update documentation_guidelines.md * doc: update testing.md * doc: update deployment guides * doc: update /dev readme * doc: update general_info * doc: add 0 value to doc weight * doc: add index.md to every doc folders * doc: add weight to index.md and move openrouter from free_ai_apis.md to ai_setup.md * doc: update toc so they display properly on the right had side in mkdocs * doc: update pandoranext.md * doc: index logging_system.md * doc: update readme.md * doc: update litellm.md * doc: update ./dev/readme.md * doc:🔖 new presets.md * doc: minor corrections * doc update: user_auth_system.md and presets.md, doc feat: add mermaid support to mkdocs * doc update: add screenshots to presets.md * doc update: add screenshots to - OpenID with AWS Cognito * doc update: BingAI cookie instruction * doc update: discord auth * doc update: facebook auth * doc: corrections to user_auth_system.md * doc update: github auth * doc update: google auth * doc update: auth clean up * doc organization: installation * doc organization: configuration * doc organization: features+plugins & update:plugins screenshots * doc organization: deploymend + general_info & update: tech_stack.md * doc organization: contributions * doc: minor fixes * doc: minor fixes
3.1 KiB
| title | weight |
|---|---|
| 🙌 Beginner's Guide to Contributions | -10 |
How to Contribute in a Quick and Easy Way
Installation of Tools
- Git is essential, the first thing to download.
- Git LFS can be useful for uploading files with larger sizes.
- Github Desktop - I use it only for UI; I don't recommend using it for pushing or other actions.
How to Use?
This will be a somewhat raw text, but I'll try to be as clear as possible.
I recommend installing the following extensions in VS Code:
Example of a Pull Request (PR)
Let's say I want to add another page for an API Panel.
- Open GitHub and select Danny's fork.
- First, make sure that the main branch is clean with no commits and up to date.
- Open "View all my branches" and create a new branch with a descriptive name for your task. For example: "ApiPanel."
- In GitHub Desktop, select the branch you just created.
- Start modifying the code, and when you finish a part, commit the changes. Example of commits:
- commit1: Created the frontend
- commit2: Fixed a bug in variable export
- commit3: Removed unnecessary comments and added translation support
- and so on...
Testing
While testing the code, if you're working with the frontend, it might be frustrating to run npm run frontend and npm run backend every time. Instead, use npm run frontend:dev to see real-time changes on port 3090 (really!).
Note: You must run
npm run frontendonce before you can usenpm run frontend:dev
How?
git add *adds all files to be committed.git commit -m "name-of-your-commit"creates a commit.git pushuploads the changes.
Before doing all this, I recommend using GitHub Desktop to see what you've changed.
If git commit fails due to ESLint errors, read the error message and understand what's wrong. It could be an unused variable or other issues.
Possible Various Problems
If you have the main branch with many commits and don't know what to do, follow this simple guide:
⚠️ Please do this only when you have no active PRs or when you're not working on the project:
- Do a pull origin and in the terminal write
git logto identify how many commits you are behind. - Use
git rebase -i HEAD~2, where 2 represents the number of commits you need to go back. If you need to go back 100 commits, usegit rebase -i HEAD~100. - In the editor, change the "pick" for the two commits to "drop," save with "esc," then type
:wqand press "Enter." - Finally, run
git push --force origin main.