chore: updates docs, readme, templates, workflow updates (#130)

.github/ISSUE_TEMPLATE/BUG-FORM.yml

@@ -14,11 +14,8 @@ body:
           description: What component is the bug in?
           multiple: true
           options:
-              - Forge
-              - Cast
-              - Anvil
-              - Foundryup
-              - Chisel
+              - zkForge
+              - zkCast
               - Other (please describe)
       validations:
           required: true

.github/ISSUE_TEMPLATE/FEATURE-FORM.yml

@@ -14,11 +14,8 @@ body:
           description: What component is the feature for?
           multiple: true
           options:
-              - Forge
-              - Cast
-              - Anvil
-              - Foundryup
-              - Chisel
+              - zkForge
+              - zkCast
               - Other (please describe)
       validations:
           required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,21 +1,17 @@
-<!--
-Thank you for your Pull Request. Please provide a description above and review
-the requirements below.
+# What :computer: 
+* First thing updated with this PR
+* Second thing updated with this PR
+* Third thing updated with this PR
 
-Bug fixes and new features should include tests.
--->
+# Why :hand:
+* Reason why first thing was added to PR
+* Reason why second thing was added to PR
+* Reason why third thing was added to PR
 
-## Motivation
+# Evidence :camera:
+Include screenshots, screen recordings, or `console` output here demonstrating that your changes work as intended
 
-<!--
-Explain the context and why you're making that change. What is the problem
-you're trying to solve? In some cases there is not a problem and this can be
-thought of as being the motivation for your change.
--->
+<!-- All sections below are optional. You can uncomment any section applicable to your Pull Request. -->
 
-## Solution
-
-<!--
-Summarize the solution and provide any necessary context needed to understand
-the code change.
--->
+<!-- # Notes :memo:
+* Any notes/thoughts that the reviewers should know prior to reviewing the code? -->

.github/workflows/check-pr-title.yml

@@ -0,0 +1,18 @@
+name: Check PR title
+on:
+  pull_request_target:
+    types:
+      - opened
+      - reopened
+      - edited
+      - synchronize
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    permissions:
+      statuses: write
+    steps:
+      - uses: aslafy-z/conventional-pr-title-action@v3
+        env:
+          GITHUB_TOKEN: ${{ github.token }}

.github/workflows/deny.yml

@@ -2,10 +2,10 @@ name: deny
 
 on:
     push:
-        branches: [master]
+        branches: [main]
         paths: [Cargo.lock, deny.toml]
     pull_request:
-        branches: [master]
+        branches: [main]
         paths: [Cargo.lock, deny.toml]
 
 env:

.github/workflows/release.yml

@@ -61,10 +61,6 @@ jobs:
               env:
                   GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
-    release-docker:
-        name: Release Docker
-        uses: ./.github/workflows/docker-publish.yml
-
     release:
         name: ${{ matrix.job.target }} (${{ matrix.job.os }})
         runs-on: ${{ matrix.job.os }}
@@ -232,7 +228,7 @@ jobs:
     issue:
         name: Open an issue
         runs-on: ubuntu-latest
-        needs: [prepare, release-docker, release, cleanup]
+        needs: [prepare, release, cleanup]
         if: ${{ failure() }}
         steps:
             - uses: actions/checkout@v3

.github/leaked_secrets.yaml → .github/workflows/secret_scanner.yaml

@@ -5,7 +5,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c # v3
+        uses: actions/checkout@v3
         with:
           fetch-depth: 0
       - name: TruffleHog OSS