Skip to content

Commit 659deb2

Browse files
authored
Merge branch 'master' into master
2 parents 85ceeba + 2bae230 commit 659deb2

File tree

3 files changed

+33
-1
lines changed

3 files changed

+33
-1
lines changed

CONTRIBUTING.md

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
![PineCoders](/images/PineCodersLong.png "PineCoders")
2+
3+
## Instructions to contributors
4+
5+
First of all, **thank you!** 💖  We hope this repo becomes the de facto reference for reusable Pine code, and this will only happen with contributions like yours.
6+
7+
You can contribute in three ways:
8+
9+
1. Do everything yourself:
10+
- Fork the repo.
11+
- Use the supplied snippet templates to format each of your snippet.
12+
- Add snippet to an existing category or in the `uncategorized` category.
13+
- Issue a pull request.
14+
1. Supply the code through GitHub without formatting your snippet:
15+
- Fork the repo.
16+
- Add your code in the `uncategorized` category.
17+
- Issue a pull request.
18+
1. If you are not familiar with GitHub, you can just send your code in a text file to [email protected]. You can use the supplied templates to format your code, but it's not mandatory.
19+
20+
We will revise and, if required, edit contributions to ensure they meet our publications standards. We will get in touch with you if we have questions.
21+
22+
### Notes
23+
- Authors are recognized in each snippet.
24+
- No coding conventions are mandatory. It's more important to share than to have uniform code. If you are interested in following a standard, use the [PineCoders Coding Conventions](http://www.pinecoders.com/coding_conventions).
25+
- Since the repo's code is meant to be used by Pine coders of all skill levels, care should be taken to document assumptions and proper use of your snippets. The example section in each snippet is often the best way to achieve that.
26+
- Templates are in the `snippets/templates` directory. There is one template for each type of snippet: *function*, *technique* and *variable*.
27+
- Formatting inside the templates is a mix of [Markdown](https://github.com/adam-p/markdown-here/wiki) and HTML.
28+
- Version 4 code is preferred. The templates allow for multiple versions of your snippets.

DISCLAIMER.md

+2
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
![PineCoders](/images/PineCodersLong.png "PineCoders")
2+
13
# DISCLAIMER
24

35
All information and code provided in this repository must be used at your own risk.

README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -5,4 +5,6 @@ Reusable Pine Script snippets and tricks & tips to help Pine Script developers.
55

66
The [PineCoders web site](http://pinecoders.com) contains links to our [Coding Conventions](http://www.pinecoders.com/coding_conventions/), [Pine FAQ & Code](http://www.pinecoders.com/faq_and_code/) and [Pine Resources](http://www.pinecoders.com/resources/).
77

8-
[Interested in contributing?](/snippets/#instructions-to-contributors)
8+
#### ⮆ [Interested in contributing?](/snippets/#instructions-to-contributors)
9+
10+
> Thanks to Alex Orekhov (a.k.a. [everget](https://www.tradingview.com/u/everget/)) and [Ricardo Santos](https://www.tradingview.com/u/RicardoSantos/) for setting up and structuring the PineCoders repo **and** contributing their precious code.

0 commit comments

Comments
 (0)