Skip to content

Commit 0377e0a

Browse files
committed
Merge pull request #2044 from mgreter/feature/github-contrib-hints
Add initial CONTRIBUTING.md and ISSUE_TEMPLATE.md
2 parents 3ae9a20 + 59e0f4e commit 0377e0a

File tree

2 files changed

+91
-0
lines changed

2 files changed

+91
-0
lines changed

.github/CONTRIBUTING.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# Contributing to LibSass
2+
3+
:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
4+
5+
The following is a set of guidelines for contributing to LibSass, which is hosted in the [Sass Organization](https://github.com/sass) on GitHub.
6+
These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a pull request.
7+
8+
LibSass is a library that implements a [sass language] [1] compiler. As such it does not directly interface with end users (frontend developers).
9+
For direct contributions to the LibSass code base you will need to have at least a rough idea of C++, we will not lie about that.
10+
But there are other ways to contribute to the progress of LibSass. All contributions are done via github pull requests.
11+
12+
You can contribute to the [LibSass documentation] [2] or provide additional [spec tests] [3] (we will gladly point you in the direction
13+
of the dirty corners in LibSass). Foremost we rely on good and concise bug reports for issues the spec tests do not yet catch.
14+
15+
[1]: http://sass-lang.com/
16+
[2]: https://github.com/sass/libsass/tree/master/docs
17+
[3]: https://github.com/sass/sass-spec

.github/ISSUE_TEMPLATE.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
## Precheck: My Sass isn't compiling
2+
- [ ] Check if you can reproduce the issue via [SourceMap Inspector] [5] (updated regularly).
3+
- [ ] Validate official ruby sass compiler via [SassMeister] [6] produces your expected result.
4+
- [ ] Search for similar issue in [LibSass] [1] and [node-sass] [2] (include closed tickets)
5+
- [ ] Optionally test your code directly with [sass] [7] or [sassc] [2] ([installer] [4])
6+
7+
## Precheck: My build/install fails
8+
- [ ] Problems with building or installing libsass should be directed to implementors first!
9+
- [ ] Except for issues directly verified via sassc or LibSass own build (make/autotools9
10+
11+
## Craft a meaningfull error report
12+
- [ ] Include the version of libsass and the implementor (i.e. node-sass or sassc)
13+
- [ ] Include information about your operating system and environment (i.e. io.js)
14+
- [ ] Either create a self contained sample that shows your issue ...
15+
- [ ] ... or provide it as a fetchable (github preferred) archive/repo
16+
- [ ] ... and include a step by step list of command to get all dependencies
17+
- [ ] Make it clear if you use indented or/and scss syntax
18+
19+
## My error is hiding in a big code base
20+
1. we do not have time to support your code base!
21+
2. to fix occuring issues we need precise bug reports
22+
3. the more precise you are, the faster we can help you
23+
4. lazy reports get overlooked even when exposing serious bugs
24+
5. it's not hard to do, it only takes time
25+
- [ ] Make sure you saved the current state (i.e. commit to git)
26+
- [ ] Start by uncommenting blocks in the initial source file
27+
- [ ] Check if the problem is still there after each edit
28+
- [ ] Repeat until the problem goes away
29+
- [ ] Inline imported files as you go along
30+
- [ ] Finished once you cannot remove more
31+
- [ ] The emphasis is on the word "repeat" ...
32+
33+
## What makes a code test case
34+
35+
Important is that someone else can get the test case up and running to reproduce it locally. For this
36+
we urge you to verify that your sample yields the expected result by testing it via [SassMeister] [6]
37+
or directly via ruby sass or node-sass (or any other libsass implementor) before submitting your bug
38+
report. Once you verified all of the above, you may use the template below to file your bug report.
39+
40+
### Title: Be as meaningfull as possible in 60 chars if possible
41+
42+
input.scss
43+
```scss
44+
test {
45+
content: bar
46+
}
47+
```
48+
49+
libsass 3.5.5
50+
```css
51+
test {
52+
content: bar; }
53+
```
54+
55+
ruby sass 3.4.21
56+
```css
57+
test {
58+
content: bar; }
59+
```
60+
61+
version info:
62+
```cmd
63+
$ node-sass --version
64+
node-sass 3.3.3 (Wrapper) [JavaScript]
65+
libsass 3.2.5 (Sass Compiler) [C/C++]
66+
```
67+
68+
[1]: https://github.com/sass/libsass/issues?utf8=%E2%9C%93&q=is%3Aissue
69+
[2]: https://github.com/sass/node-sass/issues?utf8=%E2%9C%93&q=is%3Aissue
70+
[3]: https://github.com/sass/sassc
71+
[4]: http://libsass.ocbnet.ch/installer/
72+
[5]: http://libsass.ocbnet.ch/srcmap/
73+
[6]: http://www.sassmeister.com/
74+
[7]: https://rubygems.org/gems/sass

0 commit comments

Comments
 (0)