Merge pull request #2 from Sixfold-AI/leo/set-up-github-actions

Set up GitHub Actions

.github/CODEOWNERS

@@ -0,0 +1 @@
+*       @Sixfold-AI/dev

.github/dependabot.yml

@@ -0,0 +1,15 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: 'npm'
+    directory: '/'
+    schedule:
+      interval: 'weekly'
+  - package-ecosystem: 'github-actions'
+    directory: '/'
+    schedule:
+      interval: 'weekly'

.github/pull_request_template.md

@@ -0,0 +1,52 @@
+_NOTE: When filling out this template, keep the headers and replace the content with your words or "None" or "N/A" if that section is not relevant._
+
+_For the first line of the PR, write one short sentence describing the purpose of the pull request._
+
+_In successive paragraphs, add other comments that help us understand the context, the changes, and the impact of the PR._
+
+## Developer experience changes
+
+_Explain any changes to the developer experience - build / deploy workflows, CLI commands, APIs, or events._
+
+_If there are no DX changes, write "None"._
+
+## Other changes
+
+_Describe any additional changes made to the codebase here. These might be small unrelated fixes or refactors that you made while working on this PR._
+
+_If there are no other changes, write "None"._
+
+## Screenshots
+
+_Include screenshots or videos that demonstrate the changes to a user interface (web, API, CLI)._
+
+_If there are no UI changes, write "None"._
+
+## Known issues
+
+_Add a list of issues that are still present in the codebase with regard to this feature - resiliency problems, bugs, unaddressed edge cases, missing error handling, etc. For each issue, link to the corresponding issue record in Linear if one exists._
+
+_If there are no known issues, write "None"._
+
+## Dependencies
+
+_Add a list of dependent PRs or actions that must be taken in order for the change in this PR to be effective. For each dependency, link to the corresponding PR or Linear issue._
+
+_If there are no dependencies, write "None"._
+
+## Development migration
+
+_Describe any steps that need to be taken to update the development environment after this PR is merged. For example, if you added a new environment variable, describe how to set it. If you added a new database migration, describe how to run it. If you changed a dependency, remind us to run Bundler or Yarn._
+
+
+_If no migration steps are required, write "None"._
+
+## Release plan
+
+_Describe any steps that need to be taken to update the staging or production environments after deploying the merge commit.  These steps will be merged into the overall plan for all changes going out in the next release._
+
+_Example:_
+
+> 1. Create a feature flag named `my-feature-flag` in the feature flag service and enable it for all Sixfold users.
+
+_If no migration steps are required, write "None"._

.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: Sixfold - React Active Storage Provider CI
+on:
+  push:
+    branches: ['main']
+  pull_request:
+    branches: ['main']
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Install Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: .nvmrc
+          cache: yarn
+      - name: Install Node packages
+        run: yarn install --immutable
+      - name: Lint JS code
+        run: yarn lint
+      - name: Format JS code
+        run: yarn format
+      - name: Build JS code
+        run: yarn build
+      - name: Run tests
+        run: yarn test

.nvmrc

@@ -0,0 +1 @@
+18.18.2