matter/content
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updating the wiki and adding the new post

Browse Source
This commit is contained in:
ngn
2024-02-21 23:36:29 +03:00
parent b5feb4fbbd
commit c475fd9916
7 changed files with 117 additions and 26 deletions

54
wiki/other/contribute.md

@ -10,9 +10,11 @@ page of Gitea is disabled. So in order to register an account, send a email to t
for your account (second one will be used for registration if the first one is unavailable). Then
wait for a reply containing further instructions.
**Important:** Do not use the Gitea instance for hosting your own projects/repositories, personal
repositories (A.K.A. repositories not forked for PRs) will be deleted. If you insist on creating
personal repositories your account will be deleted.
> **Important**
>
> Do not use the Gitea instance for hosting your own projects/repositories, personal
> repositories (A.K.A. repositories not forked for PRs) will be deleted. If you insist on creating
> personal repositories your account will be deleted.
## Issues
To report a bug, to ask questions or to request a feature, first find the related repository.
@ -23,6 +25,11 @@ detailed description for the issue. Finally create the issue and patiently wait
If you want to make changes and merge them to the project, first fork the related repository.
Then clone the forked repository and make the changes you want.
> **Important**
>
> Do not make multiple changes in one commit, for example adding a feature and fixing a bug
> in the same commit is a bad idea. Separate different changes to different commits
**Make sure to use correct indenting!**. MatterLinux projects uses **2 spaces** for indenting.
Configure your editor so it uses the same indenting. Here is an example configuration for the
`vim` editor:
@ -34,9 +41,44 @@ set shiftwidth=2
set smarttab
```
After making the changes, commit them with a descriptive message. Do not use long commit messages,
instead add a description to your commit. **Make sure the email you are using for signing the
commit matches with your Gitea account email.**
And here is a more extended configuration for general usage:
```
set tabstop=2
set softtabstop=0
set expandtab
set shiftwidth=2
set smarttab
set fileencoding="utf-8"
set hlsearch
set ignorecase
set mouse=a
set smartcase
set smartindent
set noswapfile
set pumheight=10
set undofile
set scrolloff=8
set sidescrolloff=8
set number
set relativenumber
set backspace=indent,eol,start
if !isdirectory("/tmp/undos")
call mkdir("/tmp/undos", "", 0700)
endif
set undodir=/tmp/undos
set undofile
syntax on
```
After making the changes, commit them using the following format:
```
<fix/feature>: <description>
```
Do not use long commit messages, instead add a description to your commit if needed. **Make sure the email you are
using for signing the commit matches with your Gitea account email.**
After pushing your changes create a pull request (PR) to the original project. Write a
detailed description for the PR, explain the changes you have made, explain why you made