mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
committed by
Reed Allman
parent
f51792ae5e
commit
ae8e87f877
@@ -30,22 +30,23 @@ Graduation: Some extensions can graduate into core if they become commonplace in
|
||||
|
||||
## How to contribute
|
||||
|
||||
* Fork the repo
|
||||
* Fix an issue or create an issue and fix it
|
||||
* Create a Pull Request that fixes the issue
|
||||
* Sign the [CLA](https://cla.fnproject.io/)
|
||||
* Good Job! Thanks for being awesome!
|
||||
1. Fork the repo
|
||||
2. Fix an issue or create an issue and fix it
|
||||
3. Create a Pull Request that fixes the issue
|
||||
4. Sign the [CLA](http://www.oracle.com/technetwork/community/oca-486395.html)
|
||||
5. Once processed, our CLA bot will automatically clear the CLA check on the PR
|
||||
6. Good Job! Thanks for being awesome!
|
||||
|
||||
## Documentation
|
||||
|
||||
When creating a Pull Request, make sure that you also update the documentation
|
||||
accordingly.
|
||||
|
||||
Most of the times, when making some behavior more explicit or adding a feature,
|
||||
a documentation update is necessary.
|
||||
Most of the time, when making some behavior more explicit or adding a feature,
|
||||
documentation update is necessary.
|
||||
|
||||
You will either update a file inside docs/ or create one. Prefer the former over
|
||||
the latter. If you are unsure, do not hesitate in open the PR with a comment
|
||||
the latter. If you are unsure, do not hesitate to open a PR with a comment
|
||||
asking for suggestions on how to address the documentation part.
|
||||
|
||||
## How to build and get up and running
|
||||
@@ -60,7 +61,7 @@ The first time after you fork or after dependencies get updated, run:
|
||||
make dep
|
||||
```
|
||||
|
||||
Then after every change, run
|
||||
Then after every change, run:
|
||||
|
||||
```sh
|
||||
make run
|
||||
|
||||
Reference in New Issue
Block a user