From dd75a3ccc990a107aa5d6a358827cecf5da5025f Mon Sep 17 00:00:00 2001
From: Guilherme Jacomini <guilherme@mixmax.com>
Date: Fri, 21 Jul 2023 10:02:19 -0300
Subject: [PATCH 1/3] chore: add PR template

---
 .github/pull_request_template.md | 65 ++++++++++++++++++++++++++++++++
 1 file changed, 65 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..8f58acb
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,65 @@
+<!-- Author/Reviewer expectations are described in the last comment -->
+
+> **Note** - Since this is a public repository, make sure that we're not publishing private data in the code, commit comments, or this PR.
+
+## 📚 Context/Description Behind The Change
+<!--
+  What changes have you made to the code, and why?
+
+  As skilled engineers, we all know how to read and interpret code, so take this opportunity
+  to be a bit more verbal about your changes.
+
+  Giving the context behind your changes will make your PR review quicker,
+  as the reviewer will not need to guess your intent.
+-->
+
+## 🚨 Potential Risks & What To Monitor After Deployment
+<!--
+  What can go wrong with this deploy?
+  Does it touch any critical services?
+  How will these changes affect adjacent code/features?
+  How will we handle any adverse issues?
+-->
+
+## 🧑‍🔬 How Has This Been Tested?
+<!--
+  Imagine: How do I (and the Reviewer):
+  How do we know this PR does what it's supposed to do?
+  How do we ensure that adjacent code/features are still working?
+  How do we evaluate the performance implications of this PR?
+-->
+
+## 🚚 Release Plan
+<!--
+  Imagine: If you had to leave in a rush, what should the backup engineer do to deploy this?
+
+  Add any tasks that need to be done before/during/after release (i.e, creating indices, deploying
+  other services, bumping modules, notifying PM or other engineers, etc).
+-->
+
+
+
+<!--
+  ## 🤝 Expectations
+
+  When Opening/Reviewing a PR, please keep in mind:
+
+  ### As the PR Author
+  - Provide all the necessary context on "Why" you have performed your changes
+  - Assume that the reviewer has no previous knowledge about the codebase: would he/she be able to
+    review it the way it is right now?
+  - If changes are extensive, break them into smaller commits that tell a story, instead of 1 commit
+    with 15 files changed.
+  - Split Refactors and New-Code-Changes into different commits, ideally: different PRs.
+  - Test your code before requesting review — unless some rare exceptions, we shouldn't ship any code
+    without testing it before.
+  - If your PR is UI related, consider adding screenshots/videos with the behavior and before/after.
+
+  ### As the PR Reviewer
+  - Be kind. Don't nitpick.
+  - Expect to have all the necessary context to review the PR on (or linked on) the PR itself.
+  - When in doubt: ask.
+  - Validate if the author's tests have any missing coverage points. Do not approve an untested PR.
+  - Pay extra attention to the "Potential Risks" and "Release Plan" sections.
+  - If the PR alters the product UI, consider checking out the branch to visually inspect it.
+-->

From aef77b09294cc6404619cd6c2165654a95570047 Mon Sep 17 00:00:00 2001
From: Guilherme Jacomini <guilherme@mixmax.com>
Date: Fri, 21 Jul 2023 11:02:21 -0300
Subject: [PATCH 2/3] chore: configure github actions

---
 .github/workflows/ci.yml | 13 +++++++++++++
 .nvmrc                   |  1 +
 2 files changed, 14 insertions(+)
 create mode 100644 .github/workflows/ci.yml
 create mode 100644 .nvmrc

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
new file mode 100644
index 0000000..5f9ad7c
--- /dev/null
+++ b/.github/workflows/ci.yml
@@ -0,0 +1,13 @@
+name: continuous-integration
+
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  checks:
+    uses: mixmaxhq/github-workflows-public/.github/workflows/checks.yml@main
diff --git a/.nvmrc b/.nvmrc
new file mode 100644
index 0000000..9293735
--- /dev/null
+++ b/.nvmrc
@@ -0,0 +1 @@
+12.22.6

From b48848b28acf282de1630e8f323d12e559478172 Mon Sep 17 00:00:00 2001
From: Guilherme Jacomini <guilherme@mixmax.com>
Date: Fri, 21 Jul 2023 11:24:30 -0300
Subject: [PATCH 3/3] chore: remove jenkinsfile

---
 Jenkinsfile | 9 ---------
 1 file changed, 9 deletions(-)
 delete mode 100644 Jenkinsfile

diff --git a/Jenkinsfile b/Jenkinsfile
deleted file mode 100644
index 6fc53e1..0000000
--- a/Jenkinsfile
+++ /dev/null
@@ -1,9 +0,0 @@
-// This name is defined in the Jenkins management console, and pulled from a github repository under
-// our mixmaxhq organization by the same name. Specify a specific tag/revision by appending it along
-// with an '@' symbol to the string literal.
-@Library('scm-service-library') _
-
-npmModulePipeline {
-  nodeVersion = '10.16.0'
-  npmVersion = '6.4.1'
-}