chore: Fix contributing

Close #199
This commit is contained in:
Mattia Astorino 2018-06-21 23:12:10 +02:00
parent b8fec9ff01
commit b9930960f0
No known key found for this signature in database
GPG key ID: 7BE552533AB6D4E2

View file

@ -10,7 +10,6 @@
- [Contributing guidelines](#contributing-guidelines) - [Contributing guidelines](#contributing-guidelines)
- [Requirements:](#requirements) - [Requirements:](#requirements)
- [Decrypt content](#decrypt-content)
- [Installing and compiling source](#installing-and-compiling-source) - [Installing and compiling source](#installing-and-compiling-source)
- [Testing the theme](#testing-the-theme) - [Testing the theme](#testing-the-theme)
- [Adding new Material Theme commands](#adding-new-material-theme-commands) - [Adding new Material Theme commands](#adding-new-material-theme-commands)
@ -21,16 +20,6 @@
- [Backers](#backers) - [Backers](#backers)
- [Sponsors](#sponsors) - [Sponsors](#sponsors)
## Decrypt content
We use git-crypt to encrypt compiler files. To contribute you need a GPG key public/private associated with your github email.
1. Export your public key by running
```gpg --output PATH/FILENAME.gpg --export ASSOCIATEDEMAIL```
2. Send the exported `.gpg` file to a contributor that will add you to the trusted people.
3. Fetch and pull then decrypt files with `git-crypt unlock` entering your key password.
## Installing and compiling source ## Installing and compiling source
First you will have to install node_modules through npm or yarn First you will have to install node_modules through npm or yarn