Add actions

.github/CODEOWNERS

@@ -0,0 +1 @@
+*       @dappnode/core

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,42 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title:
+labels:
+assignees:
+---
+
+<!--NOTE: -->
+<!--- General questions should go to the discord chat instead of the issue tracker.-->
+
+**Describe the bug**
+
+<!--A clear and concise description of what the bug is.-->
+
+**To Reproduce**
+
+<!--Steps to reproduce the behavior:
+1. Install version X
+2. Set this configuration option
+3. Do this action
+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.-->
+
+**DAppNode version:**
+
+<!--Print the DAppNode versions and info found in http://my.dappnode/#/support/report -->
+
+- Package version: <!-- v0.1.14, upstream: prysm-1.0.0-beta -->
+- OS: <!-- Ubuntu, Debian, DAppNode Mini, DAppNode Advance -->
+- Browser <!-- If applicable: Brave, Firefox, Chrome, Safari -->
+
+**Additional context**
+
+<!--Add any other context about the problem here.-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ""
+labels: ""
+assignees: ""
+---
+
+<!--NOTE: -->
+<!--- General questions should go to the discord chat instead of the issue tracker.-->
+
+**Is your feature request related to a problem? Please describe.**
+
+<!--A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]-->
+
+**Describe the solution you'd like**
+
+<!--A clear and concise description of what you want to happen.-->
+
+**Describe alternatives you've considered**
+
+<!--A clear and concise description of any alternative solutions or features you've considered.-->
+
+**Additional context**
+
+<!--Add any other context or screenshots about the feature request here.-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+<!-- For DAppNode core members, once the Pull Request is created, do not forget to:
+1.  Link issues to the PR if available
+2.  Mention dappnode core members
+3.  Add proper labels
+-->
+
+## Context
+
+> Provide context of this PR: why it was created? what does it fixes? what new feature does it provides? ...
+
+## Approach
+
+> Define the solution for the issue or feature that this PR aims to fix
+
+## Test instructions
+
+<!-- MANDATORY: please, do not skip this step, it is very importand for DAppNode team to have simple and well defined instructions on how to test this PR.
+-->

.github/workflows/main.yml

@@ -0,0 +1,35 @@
+name: "Main"
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+    branches:
+      - "master"
+      - "v[0-9]+.[0-9]+.[0-9]+"
+    paths-ignore:
+      - "README.md"
+
+jobs:
+  build-test:
+    runs-on: ubuntu-latest
+    name: Build test
+    if: github.event_name != 'push'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - run: docker-compose build
+
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    if: github.event_name == 'push'
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup node
+        uses: actions/setup-node@v4
+        with:
+          node-version: "18.x"
+      - name: Publish
+        run: npx @dappnode/dappnodesdk publish patch --dappnode_team_preset
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}