Skip to content

Commit 2d9e732

Browse files
michal-hansmichal-hans
committed
Initial commit
0 parents  commit 2d9e732

262 files changed

Lines changed: 19432 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.editorconfig‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
root = true
2+
3+
[*]
4+
end_of_line = lf
5+
insert_final_newline = false
6+
indent_style = space
7+
indent_size = 2

‎.gitattributes‎

Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
1+
# From https://github.com/Danimoth/gitattributes/blob/master/Web.gitattributes
2+
3+
# Handle line endings automatically for files detected as text
4+
# and leave all files detected as binary untouched.
5+
* text=auto
6+
7+
#
8+
# The above will handle all files NOT found below
9+
#
10+
11+
#
12+
## These files are text and should be normalized (Convert crlf => lf)
13+
#
14+
15+
# source code
16+
*.php text
17+
*.css text
18+
*.sass text
19+
*.scss text
20+
*.less text
21+
*.styl text
22+
*.js text eol=lf
23+
*.coffee text
24+
*.json text
25+
*.htm text
26+
*.html text
27+
*.xml text
28+
*.svg text
29+
*.txt text
30+
*.ini text
31+
*.inc text
32+
*.pl text
33+
*.rb text
34+
*.py text
35+
*.scm text
36+
*.sql text
37+
*.sh text
38+
*.bat text
39+
40+
# templates
41+
*.ejs text
42+
*.hbt text
43+
*.jade text
44+
*.haml text
45+
*.hbs text
46+
*.dot text
47+
*.tmpl text
48+
*.phtml text
49+
50+
# server config
51+
.htaccess text
52+
53+
# git config
54+
.gitattributes text
55+
.gitignore text
56+
.gitconfig text
57+
58+
# code analysis config
59+
.jshintrc text
60+
.jscsrc text
61+
.jshintignore text
62+
.csslintrc text
63+
64+
# misc config
65+
*.yaml text
66+
*.yml text
67+
.editorconfig text
68+
69+
# build config
70+
*.npmignore text
71+
*.bowerrc text
72+
73+
# Heroku
74+
Procfile text
75+
.slugignore text
76+
77+
# Documentation
78+
*.md text
79+
LICENSE text
80+
AUTHORS text
81+
82+
83+
#
84+
## These files are binary and should be left untouched
85+
#
86+
87+
# (binary is a macro for -text -diff)
88+
*.png binary
89+
*.jpg binary
90+
*.jpeg binary
91+
*.gif binary
92+
*.ico binary
93+
*.mov binary
94+
*.mp4 binary
95+
*.mp3 binary
96+
*.flv binary
97+
*.fla binary
98+
*.swf binary
99+
*.gz binary
100+
*.zip binary
101+
*.7z binary
102+
*.ttf binary
103+
*.eot binary
104+
*.woff binary
105+
*.pyc binary
106+
*.pdf binary

‎.github/CONTRIBUTING.md‎

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
# Contributing to react-boilerplate
2+
3+
Love react-boilerplate and want to help? Thanks so much, there's something to do for everybody!
4+
5+
Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
6+
7+
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
8+
9+
## Using the issue tracker
10+
11+
The [issue tracker](https://github.com/mxstbr/react-boilerplate/issues) is
12+
the preferred channel for [bug reports](#bugs), [features requests](#features)
13+
and [submitting pull requests](#pull-requests).
14+
15+
<a name="bugs"></a>
16+
## Bug reports
17+
18+
A bug is a _demonstrable problem_ that is caused by the code in the repository.
19+
Good bug reports are extremely helpful - thank you!
20+
21+
Guidelines for bug reports:
22+
23+
1. **Use the GitHub issue search** &mdash; check if the issue has already been reported.
24+
25+
2. **Check if the issue has been fixed** &mdash; try to reproduce it using the latest `master` or development branch in the repository.
26+
27+
3. **Isolate the problem** &mdash; ideally create a [reduced test case](https://css-tricks.com/reduced-test-cases/) and a live example.
28+
29+
A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS
30+
experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
31+
32+
Example:
33+
34+
> Short and descriptive example bug report title
35+
>
36+
> A summary of the issue and the browser/OS environment in which it occurs. If
37+
> suitable, include the steps required to reproduce the bug.
38+
>
39+
> 1. This is the first step
40+
> 2. This is the second step
41+
> 3. Further steps, etc.
42+
>
43+
> `<url>` - a link to the reduced test case
44+
>
45+
> Any other information you want to share that is relevant to the issue being
46+
> reported. This might include the lines of code that you have identified as
47+
> causing the bug, and potential solutions (and your opinions on their
48+
> merits).
49+
50+
51+
<a name="features"></a>
52+
## Feature requests
53+
54+
Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to *you* to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
55+
56+
57+
<a name="pull-requests"></a>
58+
## Pull requests
59+
60+
Good pull requests - patches, improvements, new features - are a fantastic
61+
help. They should remain focused in scope and avoid containing unrelated
62+
commits.
63+
64+
**Please ask first** before embarking on any significant pull request (e.g.
65+
implementing features, refactoring code, porting to a different language),
66+
otherwise you risk spending a lot of time working on something that the
67+
project's developers might not want to merge into the project.
68+
69+
Please adhere to the coding conventions used throughout a project (indentation,
70+
accurate comments, etc.) and any other requirements (such as test coverage).
71+
72+
Since the `master` branch is what people actually use in production, we have a
73+
`dev` branch that unstable changes get merged into first. Only when we
74+
consider that stable we merge it into the `master` branch and release the
75+
changes for real.
76+
77+
Adhering to the following process is the best way to get your work
78+
included in the project:
79+
80+
1. [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork, and configure the remotes:
81+
82+
```bash
83+
# Clone your fork of the repo into the current directory
84+
git clone https://github.com/<your-username>/react-boilerplate.git
85+
# Navigate to the newly cloned directory
86+
cd react-boilerplate
87+
# Assign the original repo to a remote called "upstream"
88+
git remote add upstream https://github.com/mxstbr/react-boilerplate.git
89+
```
90+
91+
2. If you cloned a while ago, get the latest changes from upstream:
92+
93+
```bash
94+
git checkout dev
95+
git pull upstream dev
96+
```
97+
98+
3. Create a new topic branch (off the `dev` branch) to contain your feature, change, or fix:
99+
100+
```bash
101+
git checkout -b <topic-branch-name>
102+
```
103+
104+
4. Commit your changes in logical chunks. Please adhere to these [git commit message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) or your code is unlikely be merged into the main project. Use Git's [interactive rebase](https://help.github.com/articles/about-git-rebase/) feature to tidy up your commits before making them public.
105+
106+
5. Locally merge (or rebase) the upstream dev branch into your topic branch:
107+
108+
```bash
109+
git pull [--rebase] upstream dev
110+
```
111+
112+
6. Push your topic branch up to your fork:
113+
114+
```bash
115+
git push origin <topic-branch-name>
116+
```
117+
118+
7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
119+
with a clear title and description.
120+
121+
**IMPORTANT**: By submitting a patch, you agree to allow the project
122+
owners to license your work under the terms of the [MIT License](https://github.com/mxstbr/react-boilerplate/blob/master/LICENSE.md).

‎.github/ISSUE_TEMPLATE.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# React Boilerplate
2+
3+
Before opening a new issue, please take a moment to review our [**community guidelines**](https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md) to make the contribution process easy and effective for everyone involved.
4+
5+
Please direct redux-saga related questions to stack overflow:
6+
http://stackoverflow.com/questions/tagged/redux-saga
7+
8+
For questions related to the boilerplate itself, you can also find answers on our gitter chat:
9+
https://gitter.im/mxstbr/react-boilerplate
10+
11+
**Before opening a new issue, you may find an answer in already closed issues**:
12+
https://github.com/mxstbr/react-boilerplate/issues?q=is%3Aissue+is%3Aclosed
13+
14+
## Issue Type
15+
16+
- [ ] Bug (https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md#bug-reports)
17+
- [ ] Feature (https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md#feature-requests)
18+
19+
## Description
20+
21+
(Add images if possible)
22+
23+
## Steps to reproduce
24+
25+
(Add link to a demo on https://jsfiddle.net or similar if possible)
26+
27+
# Versions
28+
29+
- Node/NPM:
30+
- Browser:

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## React Boilerplate
2+
3+
Thank you for contributing! Please take a moment to review our [**contributing guidelines**](https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md)
4+
to make the process easy and effective for everyone involved.
5+
6+
**Please open an issue** before embarking on any significant pull request, especially those that
7+
add a new library or change existing tests, otherwise you risk spending a lot of time working
8+
on something that might not end up being merged into the project.
9+
10+
Before opening a pull request, please ensure:
11+
12+
- [ ] You have followed our [**contributing guidelines**](https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md)
13+
- [ ] double-check your branch is based on `dev` and targets `dev`
14+
- [ ] Pull request has tests (we are going for 100% coverage!)
15+
- [ ] Code is well-commented, linted and follows project conventions
16+
- [ ] Documentation is updated (if necessary)
17+
- [ ] Internal code generators and templates are updated (if necessary)
18+
- [ ] Description explains the issue/use-case resolved and auto-closes related issues
19+
20+
Be kind to code reviewers, please try to keep pull requests as small and focused as possible :)
21+
22+
**IMPORTANT**: By submitting a patch, you agree to allow the project
23+
owners to license your work under the terms of the [MIT License](https://github.com/mxstbr/react-boilerplate/blob/master/LICENSE.md).

‎.gitignore‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# Don't check auto-generated stuff into git
2+
coverage
3+
build
4+
node_modules
5+
stats.json
6+
7+
# Cruft
8+
.DS_Store
9+
npm-debug.log
10+
.idea

‎.travis.yml‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
language: node_js
2+
3+
node_js:
4+
- 6
5+
- 5
6+
- 4
7+
8+
script: npm run build
9+
10+
install:
11+
- npm i -g npm@latest
12+
- npm install
13+
14+
before_install:
15+
- export CHROME_BIN=chromium-browser
16+
- export DISPLAY=:99.0
17+
- sh -e /etc/init.d/xvfb start
18+
19+
notifications:
20+
email:
21+
on_failure: change
22+
23+
after_success: 'npm run coveralls'
24+
25+
cache:
26+
directories:
27+
- node_modules

‎CODE_OF_CONDUCT.md‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
# Contributor Code of Conduct
2+
3+
As contributors and maintainers of this project, and in the interest of
4+
fostering an open and welcoming community, we pledge to respect all people who
5+
contribute through reporting issues, posting feature requests, updating
6+
documentation, submitting pull requests or patches, and other activities.
7+
8+
We are committed to making participation in this project a harassment-free
9+
experience for everyone, regardless of level of experience, gender, gender
10+
identity and expression, sexual orientation, disability, personal appearance,
11+
body size, race, ethnicity, age, religion, or nationality.
12+
13+
Examples of unacceptable behavior by participants include:
14+
15+
* The use of sexualized language or imagery
16+
* Personal attacks
17+
* Trolling or insulting/derogatory comments
18+
* Public or private harassment
19+
* Publishing other's private information, such as physical or electronic
20+
addresses, without explicit permission
21+
* Other unethical or unprofessional conduct
22+
23+
Project maintainers have the right and responsibility to remove, edit, or
24+
reject comments, commits, code, wiki edits, issues, and other contributions
25+
that are not aligned to this Code of Conduct, or to ban temporarily or
26+
permanently any contributor for other behaviors that they deem inappropriate,
27+
threatening, offensive, or harmful.
28+
29+
By adopting this Code of Conduct, project maintainers commit themselves to
30+
fairly and consistently applying these principles to every aspect of managing
31+
this project. Project maintainers who do not follow or enforce the Code of
32+
Conduct may be permanently removed from the project team.
33+
34+
This Code of Conduct applies both within project spaces and in public spaces
35+
when an individual is representing the project or its community.
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
38+
reported by contacting the project maintainer at contact@mxstbr.com. All
39+
complaints will be reviewed and investigated and will result in a response that
40+
is deemed necessary and appropriate to the circumstances. Maintainers are
41+
obligated to maintain confidentiality with regard to the reporter of an
42+
incident.
43+
44+
45+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
46+
version 1.3.0, available at
47+
[http://contributor-covenant.org/version/1/3/0/][version]
48+
49+
[homepage]: http://contributor-covenant.org
50+
[version]: http://contributor-covenant.org/version/1/3/0/

0 commit comments

Comments
 (0)