krak/zstd
krak/zstd
1
0
Fork 0
mirror of https://github.com/facebook/zstd.git synced 2025-03-06 16:56:49 +02:00
Code Issues Releases 1 Activity

Remove redundant section and typo

Browse Source
This commit is contained in:
Bimba Shrestha 2020-02-18 14:21:19 -08:00
parent 042b28bd2c
commit 8f8c53d995
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CONTRIBUTING.md
View File

@ -93,7 +93,7 @@ Our contribution process works in three main stages:
* You will have to iterate on your changes with feedback from other collaborators to reach a point * You will have to iterate on your changes with feedback from other collaborators to reach a point
where your pull request can be safely merged. where your pull request can be safely merged.
* To avoid too many comments on style and convention, make sure that you have a * To avoid too many comments on style and convention, make sure that you have a
look at your style section below before creating a pull request. look at our style section below before creating a pull request.
* Eventually, someone from the zstd team will approve your pull request and not long after merge it into * Eventually, someone from the zstd team will approve your pull request and not long after merge it into
the dev branch. the dev branch.
* Housekeeping: * Housekeeping:
@ -106,9 +106,6 @@ Our contribution process works in three main stages:
their change makes it to the next release of zstd. Users will often discover bugs in your code or their change makes it to the next release of zstd. Users will often discover bugs in your code or
suggest ways to refine and improve your initial changes even after the pull request is merged. suggest ways to refine and improve your initial changes even after the pull request is merged.
## Zstandard style and conventions
## Setting up continuous integration (CI) on your fork ## Setting up continuous integration (CI) on your fork
Zstd uses a number of different continuous integration (CI) tools to ensure that new changes Zstd uses a number of different continuous integration (CI) tools to ensure that new changes
are well tested before they make it to an official release. Specifically, we use the platforms are well tested before they make it to an official release. Specifically, we use the platforms