added .github folder

Author: Pesekjak

.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -0,0 +1,44 @@
+name: "Bug Report"
+description: Create a new ticket for a bug.
+title: "[BUG] - <title>"
+labels: [
+    "bug"
+]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: "Description"
+      description: Please enter an explicit description of your issue.
+      placeholder: Short and explicit description of your incident.
+    validations:
+      required: true
+  - type: textarea
+    id: reprod
+    attributes:
+      label: "Reproduction steps"
+      description: Please enter an explicit description of your issue.
+      value: |
+        1. Go to '...'
+        2. Click on '....'
+        3. See error
+        ...
+      render: bash
+    validations:
+      required: true
+  - type: textarea
+    id: screenshot
+    attributes:
+      label: "Screenshots"
+      description: If applicable, add screenshots to help explain your problem.
+      render: bash
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: "Logs"
+      description: Please copy and paste any relevant log output.
+      render: bash
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml

@@ -0,0 +1,39 @@
+name: "Feature Request"
+description: Create a new ticket for a new feature request
+title: "[REQUEST] - <title>"
+labels: [
+    "question"
+]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: "Summary"
+      description: Provide a brief explanation of the feature.
+      placeholder: Describe in a few lines your feature request.
+    validations:
+      required: true
+  - type: textarea
+    id: basic_example
+    attributes:
+      label: "Basic Example"
+      description: Indicate here some basic examples of your feature.
+      placeholder: A few specific words about your feature request.
+    validations:
+      required: true
+  - type: textarea
+    id: drawbacks
+    attributes:
+      label: "Why"
+      description: Why you want to see this feature added?
+      placeholder: How would this feature be benefitial for Machine.
+    validations:
+      required: true
+  - type: textarea
+    id: unresolved_question
+    attributes:
+      label: "Unresolved questions"
+      description: What questions still remain unresolved?
+      placeholder: Identify any unresolved issues.
+    validations:
+      required: false

.github/assets/social_banner.png

@@ -0,0 +1,37 @@
+**PLEASE REMOVE THIS PART BEFORE SUBMITTING YOUR PR**
+
+Please, go through these steps before you submit a PR.
+
+1. Make sure that your PR is not a duplicate.
+2. If not, then make sure that:
+    - You have done your changes in a separate branch.
+    - You have a descriptive commit message with a short title (first line).
+    - You have only one commit (if not, squash them into one commit).
+    - You follow contributing guide lines; [CONTRIBUTING.md](../CONTRIBUTING.md) and [STYLE_GUIDE.md](../STYLE_GUIDE.md).
+    - Tests don't throw any error. If they do, fix them first.
+    - Check style doesn't throw any error. If it does fix the style of the code.
+    - Header is part of all code files (for java files this is done automatically when project is built).
+
+3. **After** these steps, you're ready to open a pull request.
+   - Give a descriptive title to your PR.
+   - Describe your changes, use following template.
+   - Put `closes #XXXX` in your comment fixed specific issue.
+
+**PLEASE USE THIS TEMPLATE FOR YOUR PR**
+
+**What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
+
+
+**What is the current behavior?** (You can also link to an open issue here)
+
+
+**What is the new behavior?** (If this is a feature change)
+
+
+**Does this PR introduce a breaking change?** (What changes might users need to make due to this PR?)
+
+
+**Other information**: (Remove if empty)
+
+
+* [ ] I follow Machine contributing guidelines

.github/pull_request_template.md

@@ -0,0 +1,31 @@
+name: Build and test Machine
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Set up JDK 17
+        uses: actions/setup-java@v3
+        with:
+          distribution: 'adopt'
+          java-version: 17
+          cache: gradle
+      - name: Grant execute permission for gradlew
+        run: chmod +x gradlew
+      - name: Build Machine
+        run: ./gradlew buildAll
+      - name: Upload Nightly Build
+        uses: actions/upload-artifact@v3
+        if: success()
+        with:
+          name: Machine
+          path: build/libs/*.jar

.github/workflows/tests.yml

@@ -11,7 +11,7 @@ much appreciated!
 
 ### General Information
 - Adhere to the project's style guide, which is comprehensively
-described in the `STYLE_GUIDE.md` file.
+described in the [STYLE_GUIDE.md](STYLE_GUIDE.md) file.
 - Test your modifications carefully, make sure they don't cause
 side effects that may cause unintentional behaviour.
 - Contributions must not include any malicious code intended to cause harm to
@@ -66,14 +66,17 @@ When designing implementations, ensure that you:
   such as unexpected exceptions.
 
 ### Licensing
-In order to contribute code, it must be licensed under **GPLv3**;
+In order to contribute code, it must be licensed under [**GPLv3**](LICENSE);
 it is either your property, or you have express permission to provide
 and license it to us.
 
 Third-party code may be accepted in the following circumstances:
 - It is under a compatible license and part of a public, freely-available resource.
 - You have been granted permission to include it.
 
+All code files should start with the [Machine project header](HEADER.txt).
+For Java files, this is done automatically when the project is built.
+
 ### Lombok
 Throughout the project, we use [Lombok](https://projectlombok.org/)
 to minimize boilerplate code and improve its readability.