Pre-version 0.3beta

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Bug description
+
+**Describe the bug**: a clear and concise description of what the bug is.
+
+## Steps to reproduce it
+
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature-implementation.md

@@ -0,0 +1,15 @@
+---
+name: Feature Implementation
+about: Use this template for issues related to the documentation TODOs page.
+title: "[IMPL] "
+labels: implementation
+assignees: ''
+
+---
+
+## Implementation description
+
+## Expected behavior
+
+
+## Tests

.github/ISSUE_TEMPLATE/roadmap-item.md

@@ -0,0 +1,14 @@
+---
+name: Roadmap item
+about: Describe this issue template's purpose here.
+title: "[ROADMAP]"
+labels: roadmap
+assignees: ''
+
+---
+
+## Item Goals
+
+## Dependency
+
+## Description

.github/workflows/ci.yml

@@ -2,7 +2,7 @@ name: ci_gh-pages
 on:
   push:
     branches:
-      - dev/python_impl/minimal_lang
+      - main
 permissions:
   contents: write
 jobs:
@@ -25,4 +25,4 @@ jobs:
           restore-keys: |
             mkdocs-material-
       - run: pip install mkdocs-material mkdocstrings markdown-exec
-      - run: mkdocs gh-deploy --force
+      - run: mkdocs gh-deploy --force

.github/workflows/pre-commit.yml

@@ -0,0 +1,21 @@
+name: pre-commit
+
+on:
+  pull_request:
+    branches: [main, dev/python]
+  push:
+    branches: [main, dev/python]
+
+jobs:
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    - uses: actions/setup-python@v3
+      with:
+        python-version: '3.12'
+    - name: Run pre-commit
+      working-directory: python
+      run: |
+        pip install pre-commit
+        pre-commit run --all-files

.github/workflows/pytest.yml

@@ -0,0 +1,30 @@
+name: pytest
+
+on:
+  push:
+    branches: [main, dev/python]
+  pull_request:
+    branches: [main, dev/python]
+
+jobs:
+  build:
+    name: Run pytest
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12"]
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        working-directory: python
+        run: |
+          pip install ".[all,dev]"
+      - name: Run tests
+        working-directory: python
+        run: |
+          pytest .

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+# Contributing to H-hat
+
+You can check the issues in the [H-hat issue's page](https://github.com/hhat-lang/hhat_lang/issues) and try contributing on the issues with [good first issue](https://github.com/hhat-lang/hhat_lang/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22) label. Depending on the programming language you are using, some formatting styles and checks are required. For instance:
+- Python:
+  - Pull Request (PR) code should follow formatting from [pre-commit configuration](python/.pre-commit-config.yaml) and [pyproject](python/pyproject.toml).
+- Rust:
+  - No specific formatting style or checks other than rust formatter and analyzer.
+
+Additionally to code contribution, you are encourage to make part of discussions involving how H-hat can handle some language features or concepts. Reach us out at the [Discord](http://discord.unitary.foundation)'s `#h-hat` channel to learn more on how to contribute on that and also to chill and chat, if you feel like doing so.
+
+
+## AI Contributions
+
+The rise of Generative AI brought many advancements for newcomers to start writing code, but also created concerning situations when incorporating AI-generated code to repositories. Regardless whether you choose to use the tool or not, the code you put in a PR is your responsibility. Make sure you checked it is doing what is intended to do, and does not introduce unnecessary complexity or bugs to the existing codebase. Simply AI prompted code will not be accepted. You are required to evaluate the intent of existing issue or PR, the existing codebase, and the code you are bringing up. Should your PR produce automated AI content (description and content) without support of your critical thinking, it will be closed.    

README.md

@@ -97,17 +97,9 @@ MIT
 
 ## How to Contribute
 
-!!! info "Important"
-
-    Please read this documentation before to understand how the repository is organized and how the language structure works.
-
-You can check the [TODOs.md](TODOs.md) page to see what is listed to be done. There (probably) are issues in the [H-hat issue's page](https://github.com/hhat-lang/hhat_lang/issues) that you may want to check and try to solve/implement as well. 
-
-
-At last, reach us out at the [Discord](http://discord.unitary.foundation)'s `#h-hat` channel to
-learn more on how to contribute and chat, if you feel like doing so.
+Read [How to Contribute](CONTRIBUTING.md).
 
 ## Code of Conduct
 
 We coexist in the same world. So be nice to others as you expect others to be nice to you :)
- the same world. So be nice to others as you expect others to be nice to you :)
+ the same world. So be nice to others as you expect others to be nice to you :)