chore: add github actions

.github/ISSUE_TEMPLATE/---bug-report.md

@@ -6,28 +6,23 @@ labels: 'bug'
 assignees: ''
 
 ---
+<!--- Provide a general summary in the title above. -->
 
-<!--
-  Hi there! Thank you for discovering and submitting an issue.
+<!--- This template is entirely optional and can be removed, but is here to help both you and us. -->
+<!--- Anything on lines wrapped in comments like these will not show up in the final text. -->
 
-  Before you submit this; let's make sure of a few things.
-  Please make sure the following boxes are ticked if they are correct.
-  If not, please try and fulfill these first.
--->
+## Checklist
 
 <!-- Checked checkbox should look like this: [x] -->
-- [ ] I am on the [latest](https://github.com/xoe-labs/dodoo/releases/latest) doDoo version.
-- [ ] I have searched the [issues](https://github.com/xoe-labs/dodoo/issues) of this repo and believe that this is not a duplicate.
-- [ ] If an exception occurs when executing a command, I executed it again in debug mode (`-vvv` option).
+- [ ] On the [latest](https://github.com/xoe-labs/dodoo/releases/latest) doDoo version.
+- [ ] I have searched the [issues](https://github.com/xoe-labs/dodoo/issues) and believe that this is not a duplicate.
+- [ ] I have executed the command in debug mode (`-vvv` option) and linked log output in a gist.
 
-<!--
-  Once those are done, if you're able to fill in the following list with your information,
-  it'd be very helpful to whoever handles the issue.
--->
 
-- **OS version and name**: <!-- Replace with version + name -->
-- **doDoo version**: <!-- Replace with version -->
-- **Link of a [Gist](https://gist.github.com/) with traceback**: <!-- Gist Link Here -->
+- **OS name**: <!-- put here -->
+- **`dodoo --version`**: <!-- paste output here -->
+- **[Gist](https://gist.github.com/) with traceback / log output**: <!-- link here -->
 
-## Issue
-<!-- Now feel free to write your issue, but please be descriptive! Thanks again 🙌 ❤️ -->
+## Description
+
+<!--- Describe the bug in detail here. -->

.github/ISSUE_TEMPLATE/---documentation.md

@@ -1,22 +1,21 @@
 ---
 name: "\U0001F4DA Documentation"
-about: Did you find errors, problems, or anything unintelligible in the docs (https://github.com/xoe-labs/dodoo#readme)?
+about: Errors, problems, or unintelligible sections in the docs?
 title: ''
 labels: 'documentation'
 assignees: ''
 
 ---
+<!--- Provide a general summary in the title above. -->
 
-<!--
-  Hi there! Thank you for discovering and submitting an issue with our documentation.
+<!--- This template is entirely optional and can be removed, but is here to help both you and us. -->
+<!--- Anything on lines wrapped in comments like these will not show up in the final text. -->
 
-  Before you submit this; let's make sure of a few things.
-  Please make sure the following boxes are ticked if they are correct.
-  If not, please try and fulfill these first.
--->
+## Checklist
 
 <!-- Checked checkbox should look like this: [x] -->
-- [ ] I have searched the [issues](https://github.com/xoe-labs/dodoo/issues) of this repo and believe that this is not a duplicate.
+- [ ] I have searched the [issues](https://github.com/xoe-labs/dodoo/issues) and believe that this is not a duplicate.
 
-## Issue
-<!-- Now feel free to write your issue, but please be descriptive! Thanks again 🙌 ❤️ -->
+## Description
+
+<!--- Describe the doc issue in detail here. Link relevant lines wherever possible. -->

.github/ISSUE_TEMPLATE/---everything-else.md

@@ -8,10 +8,14 @@ labels: ''
 assignees: ''
 
 ---
+<!--- Provide a general summary in the title above. -->
 
-<!-- Describe your question and issue here. This space is meant to be used for general questions that are neither bugs, feature requests, nor documentation issues. A good example would be a question regarding doDoo's roadmap, for example. If you're looking for help when it comes to using doDoo, consider posting a question on StackOverflow instead: http://stackoverflow.com/questions/tagged/dodoo or join the dodo Matrix Chat: -->
+<!--- StackOverflow: https://stackoverflow.com/questions/tagged/dodoo -->
+<!--- Matrix Chat: https://matrix.to/#/%23dodoo:matrix.org-->
 
 
+## Checklist
+
 <!-- Checked checkbox should look like this: [x] -->
 - [ ] I have searched the [issues](https://github.com/xoe-labs/dodoo/issues) of this repo and believe that this is not a duplicate.
 - [ ] I have searched the [documentation](https://github.com/xoe-labs/dodoo#readme) and believe that my question is not covered.

.github/ISSUE_TEMPLATE/---feature-request.md

@@ -6,18 +6,17 @@ labels: 'enhancement'
 assignees: ''
 
 ---
+<!--- Provide a general summary in the title above. -->
 
-<!--
-  Hi there! Thank you for wanting to make Poetry better.
+<!--- This template is entirely optional and can be removed, but is here to help both you and us. -->
+<!--- Anything on lines wrapped in comments like these will not show up in the final text. -->
 
-  Before you submit this; let's make sure of a few things.
-  Please make sure the following boxes are ticked if they are correct.
-  If not, please try and fulfill these first.
--->
+## Checklist
 
 <!-- Checked checkbox should look like this: [x] -->
-- [ ] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate.
+- [ ] I have searched the [issues](https://github.com/xoe-labs/dodoo/issues) and believe that this is not a duplicate.
 - [ ] I have searched the [documentation](https://github.com/xoe-labs/dodoo#readme) and believe that my question is not covered.
 
 ## Feature Request
-<!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ -->
+
+<!--- Describe your idea for improvement in detail. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+<!--- Provide a general summary of your changes in the title above. -->
+
+<!--- This template is entirely optional and can be removed, but is here to help both you and us. -->
+<!--- Anything on lines wrapped in comments like these will not show up in the final text. -->
+
+## Description
+
+<!--- Describe your changes in detail here. -->
+
+## Types of Changes
+
+<!--- What types of changes does your pull request introduce? Put an `x` in all the boxes that apply. -->
+- [ ] Core
+- [ ] Bugfix
+- [ ] New feature
+- [ ] Enhancement/optimization
+- [ ] Documentation
+
+## Issues Fixed or Closed by This PR
+
+*
+
+## Checklist
+
+<!-- Checked checkbox should look like this: [x] -->
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] I have read the CONTRIBUTING document.
+- [ ] I have added tests to cover my changes.
+- [ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).
+
+## Release
+- [ ] I have added a RELEASE.md file according to [AutoPub Docs](https://github.com/autopub/autopub#release-files.)

.github/config.yml

@@ -0,0 +1,19 @@
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  Thanks for opening your first issue here! Be sure to follow the issue template!
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  Thanks for opening this pull request! Please check out our contributing guidelines.
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  Congrats on merging your first pull request! We here at xoe-labs are very thankful for your effort!
+
+# It is recommend to include as many gifs and emojis as possible

.github/release-drafter.yml

@@ -0,0 +1,11 @@
+categories:
+  - title: 🚀 Features
+    label: feature
+  - title: 🐛 Bug Fixes
+    label: fix
+  - title: 🧰 Maintenance
+    label: chore
+template: |
+  ## Changes
+
+  $CHANGES

.github/settings.yml

@@ -0,0 +1,117 @@
+# These settings are synced to GitHub by https://probot.github.io/apps/settings/
+
+repository:
+  # See https://developer.github.com/v3/repos/#edit for all available settings.
+
+  # The name of the repository. Changing this will rename the repository
+  name: dodoo
+
+  # A short description of the repository that will show up on GitHub
+  description: A suck-less Odoo server middleware; batteries included.
+
+  # A URL with more information about the repository
+  homepage: ""
+
+  # A comma-separated list of topics to set on the repository
+  topics: odoo, devops
+
+  # Either `true` to make the repository private, or `false` to make it public.
+  private: false
+
+  # Either `true` to enable issues for this repository, `false` to disable them.
+  has_issues: true
+
+  # Either `true` to enable projects for this repository, or `false` to disable them.
+  # If projects are disabled for the organization, passing `true` will cause an API error.
+  has_projects: true
+
+  # Either `true` to enable the wiki for this repository, `false` to disable it.
+  has_wiki: false
+
+  # Either `true` to enable downloads for this repository, `false` to disable them.
+  has_downloads: true
+
+  # Updates the default branch for this repository.
+  default_branch: master
+
+  # Either `true` to allow squash-merging pull requests, or `false` to prevent
+  # squash-merging.
+  allow_squash_merge: true
+
+  # Either `true` to allow merging pull requests with a merge commit, or `false`
+  # to prevent merging pull requests with merge commits.
+  allow_merge_commit: false
+
+  # Either `true` to allow rebase-merging pull requests, or `false` to prevent
+  # rebase-merging.
+  allow_rebase_merge: true
+
+# Labels: define labels for Issues and Pull Requests
+labels:
+  - name: bug
+    color: CC0000
+    description: An issue with the system 🐛.
+
+  - name: feature
+    # If including a `#`, make sure to wrap it with quotes!
+    color: '#336699'
+    description: New functionality.
+
+  - name: first-timers-only
+    # include the old name to rename an existing label
+    oldname: Help Wanted
+
+# Milestones: define milestones for Issues and Pull Requests
+milestones:
+  - title: v2.0.0
+    description: consolidating new dodoo
+    # The state of the milestone. Either `open` or `closed`
+    state: open
+
+# Collaborators: give specific users access to this repository.
+collaborators:
+  - username: blaggacao
+    # Note: Only valid on organization-owned repositories.
+    # The permission to grant the collaborator. Can be one of:
+    # * `pull` - can pull, but not push to or administer this repository.
+    # * `push` - can pull and push, but not administer this repository.
+    # * `admin` - can pull, push and administer this repository.
+    permission: admin
+
+# NOTE: The APIs needed for teams are not supported yet by GitHub Apps
+# https://developer.github.com/v3/apps/available-endpoints/
+# teams:
+#   - name: core
+#     permission: admin
+#   - name: docs
+#     permission: push
+
+branches:
+  - name: master
+    # https://developer.github.com/v3/repos/branches/#update-branch-protection
+    # Branch Protection settings. Set to null to disable
+    protection:
+      # Required. Require at least one approving review on a pull request, before merging. Set to null to disable.
+      required_pull_request_reviews:
+        # The number of approvals required. (1-6)
+        required_approving_review_count: 1
+        # Dismiss approved reviews automatically when a new commit is pushed.
+        dismiss_stale_reviews: true
+        # Blocks merge until code owners have reviewed.
+        require_code_owner_reviews: true
+        # Specify which users and teams can dismiss pull request reviews. Pass an empty dismissal_restrictions object to disable. User and team dismissal_restrictions are only available for organization-owned repositories. Omit this parameter for personal repositories.
+        dismissal_restrictions:
+          users: []
+          teams: []
+      # Required. Require status checks to pass before merging. Set to null to disable
+      required_status_checks:
+        # Required. Require branches to be up to date before merging.
+        strict: true
+        # Required. The list of status checks to require in order to merge into this branch
+        contexts: []
+      # Required. Enforce all configured restrictions for administrators. Set to true to enforce required status checks for repository administrators. Set to null to disable.
+      enforce_admins: true
+      # Required. Restrict who can push to this branch. Team and user restrictions are only available for organization-owned repositories. Set to null to disable.
+      restrictions:
+        users: []
+        teams: []