Merge pull request #1 from reason-react-native/template

Author: MoOx

.editorconfig

@@ -0,0 +1,9 @@
+# https://EditorConfig.org
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+indent_style = space
+indent_size = 2

.gitattributes

@@ -0,0 +1,3 @@
+# Tell github that .re and .rei files are Reason, sometimes recognized as C/C++
+*.re linguist-language=Reason
+*.rei linguist-language=Reason

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,61 @@
+---
+name: "\U0001F41B Bug report"
+about: "If something isn't working as expected \U0001F914"
+---
+
+<!--
+# Thank you for reporting an issue.
+
+Please note that an issue must include the information
+that is marked as REQUIRED below, or it may be closed.
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can. Try to include sample code that *anyone* could run to reproduce what you were seing
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+-->
+
+## The problem
+
+<!--
+REQUIRED: A clear and concise description of the bug or problem.
+-->
+
+### How to reproduce
+
+<!--
+Create a test case if possible
+-->
+
+Steps to reproduce:
+
+1.
+
+## Expected behavior
+
+<!--
+REQUIRED: A clear and concise description of what you expected to happen.
+-->
+
+## Actual behavior
+
+<!--
+REQUIRED: A clear and concise description of what is currently happening.
+-->
+
+## Environment
+
+Please include all necessary versions & relevant informations
+
+<!--
+OPTIONAL:
+
+## Additional context
+
+Add any other context about the problem here.
+-->

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,36 @@
+---
+name: "\U0001F680 Feature request"
+about: If you have a suggestion
+---
+
+## The problem
+
+<!--
+Please include here a clear and concise description of what the problem is.
+
+e.g.:
+
+I have an issue when [...] 
+-->
+
+## Considered solution
+
+<!--
+If possible, include a clear and concise description of what you want to happen.
+Add any considered drawbacks.
+-->
+
+## Alternatives solutions
+
+<!--
+if possible, include a clear and concise description of any alternative solutions
+or features you've considered.
+-->
+
+<!--
+OPTIONAL:
+
+## Additional context
+
+Add any other context about the problem here.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+<!--
+
+**Before submitting a pull request,** please make you followed our CONTRIBUTING guide
+
+https://github.com/reason-react-native/__template__/blob/master/CONTRIBUTING.md
+
+-->
+
+Closes #<number-of-the-issue>
+
+<!--
+Add any information that might be useful
+-->

.github/workflows/build.yml

@@ -0,0 +1,30 @@
+name: Build
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version:
+          - 8.x
+          - 10.x
+          - 12.x
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: Install
+        run: |
+          yarn install \
+            --non-interactive \
+            --frozen-lockfile
+      - name: Test
+        run: yarn test
+        env:
+          CI: true

.gitignore

@@ -0,0 +1,17 @@
+*.log
+
+# macOS crap
+.DS_Store
+
+# node
+node_modules
+
+# npm unused lock file (we use yarn.lock)
+package-lock.json
+
+# Ocaml / Reason / BuckleScript artifacts
+#*.bs.js # we do want this files to ensure zero-cost
+.bsb.lock
+**/lib/bs
+**/lib/ocaml
+**/.merlin

.prettierignore

@@ -0,0 +1,2 @@
+*.bs.js
+package.json

CHANGELOG.md

@@ -0,0 +1,17 @@
+# Changelog of `@reason-react-native/__template__`
+
+## X.Y.Z - 20YY-MM-DD
+
+Short & concise description
+
+### 💥 Breaking changes
+
+- Something, in [1234567](<link to commit on github>) by @<usename>
+
+### 🐛 Fixes
+
+- Something else, in [1234567](<link to commit on github>) by @<usename>
+
+### Internal changes
+
+(If worth mentioning)

CODE_OF_CONDUCT.md

@@ -0,0 +1,78 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and our
+community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, nationality,
+personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <opensource-conduct@moox.io>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an
+incident. Further details of specific enforcement policies may be posted
+separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq