HowToFilePR

HOME > HowToFilePR

HowToFilePR

Thank you for your PR, please follow this guide.

Rules

• Never use your 4.0release or develop branch, use bugfix/bug-summary for each PR.
• Don't close PR when update, only update the branch bugfix/bug-summary, simple enough.
• Be focus, one PR fixes exactly one bug/feature, without any noise like space or dead codes.
• Please study Pro Git, it's a very important and basic skill for open-source developer.

File New PR

The workflow to patch 4.0release or any other branches:

Step 1: Fork SRS

Open ossrs/srs, click Fork to your repository.

Step 2: Clone your repository

git clone git@github.com:your-account/srs.git
git checkout -b master origin/master
cd srs

Note: You should setup your git user.name and user.email.

Step 3: Add a remote srs

git remote add srs https://github.com/ossrs/srs.git
git fetch srs

Step 4: Sync with remote before each PR

git fetch --all

Step 5: Checkout a new branch from srs

git checkout -b bugfix/bug-summary srs/4.0release

Note: Please name your branch, by summary of bug, for example bugfix/rtc-listen-ipv6

Step 6: Update and push to your repository

git push -u origin bugfix/bug-summary

Note: Please use English in code, logs, commit and other text.

Step 7: File a PR from your bugfix/bug-summary to SRS 4.0release

Update Your PR

After review, you might need to update your PR:

git checkout bugfix/bug-summary
git commit -am 'Description for update'
git push

Note: Don't file a new PR, what you need to do is to commit to your branch, the PR will be updated automatically by GitHub.

Setup Your Email

Please setup your GitHub: Email, please DONOT select the Keep my email addresses private, which makes the commit with strange email address.

And setup user for git commit by:

cd ~/git/srs
git config --local user.name "username"
git config --local user.email "useremail@xxx.com"
git config --list

Please setup these settings to ensure you're in the SRS: Contributors.