[Snyk] Security upgrade github-pages from 228 to 229

.devcontainer/devcontainer.json

@@ -0,0 +1,5 @@
+{
+  "tasks": {
+    "build": "gem install bundler && bundle install"
+  }
+}

.github/CONTRIBUTING.md

@@ -1,3 +1,16 @@
 Please review [EIP-1](https://eips.ethereum.org/EIPS/eip-1) for EIP guidelines.
 
 <!-- RATIONALE FOR THIS FILE: IT IS DISPLAYED WHEN YOU CREATE AN ISSUE OR MAKE A PR -->
+
+## Consistency in Style and Terminology
+
+To ensure consistency in style and terminology throughout the documentation, please follow these guidelines:
+
+* Use the same terminology and phrasing as found in existing documentation.
+* Maintain a consistent tone and style in your writing.
+* Use proper formatting for headings, subheadings, and bullet points.
+* Ensure that all links and references are accurate and up-to-date.
+
+## Continuous Improvement
+
+We encourage feedback and continuous improvement of the documentation. If you have any suggestions or notice any issues, please open an issue or submit a pull request with your proposed changes.

.github/ISSUE_TEMPLATE.md

@@ -1,6 +1,6 @@
 ATTENTION! If you would like to submit an EIP and it has already been written as a draft (see the [template](https://github.com/ethereum/EIPs/blob/master/eip-template.md) for an example), please submit it as a [Pull Request](https://github.com/ethereum/EIPs/pulls).
 
-If you are considering a proposal but would like to get some feedback on the idea before submitting a draft, then continue opening an Issue as a thread for discussion.  Note that the more clearly and completely you state your idea the higher the quality of the feedback you are likely to receive.
+If you are considering a proposal but would like to get some feedback on the idea before submitting a draft, then continue opening an Issue as a thread for discussion. Note that the more clearly and completely you state your idea the higher the quality of the feedback you are likely to receive.
 
 Keep in mind the following guidelines from [EIP-1](https://eips.ethereum.org/EIPS/eip-1):
 
@@ -9,3 +9,16 @@ Keep in mind the following guidelines from [EIP-1](https://eips.ethereum.org/EIP
 > Vetting an idea publicly before going as far as writing an EIP is meant to save the potential author time. Asking the Ethereum community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Ethereum is used.
 
 > Once the champion has asked the Ethereum community as to whether an idea has any chance of acceptance, a draft EIP should be presented as a Pull Request. This gives the author a chance to flesh out the draft EIP to properly format it, ensure it is high quality, and address initial concerns about the proposal.
+
+## Consistency in Style and Terminology
+
+To ensure consistency in style and terminology throughout the documentation, please follow these guidelines:
+
+* Use the same terminology and phrasing as found in existing documentation.
+* Maintain a consistent tone and style in your writing.
+* Use proper formatting for headings, subheadings, and bullet points.
+* Ensure that all links and references are accurate and up-to-date.
+
+## Continuous Improvement
+
+We encourage feedback and continuous improvement of the documentation. If you have any suggestions or notice any issues, please open an issue or submit a pull request with your proposed changes.

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -27,3 +27,18 @@ body:
       label: Relevant log output
       description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
       render: shell
+  - type: markdown
+    attributes:
+      value: |
+        ## Consistency in Style and Terminology
+
+        To ensure consistency in style and terminology throughout the documentation, please follow these guidelines:
+
+        * Use the same terminology and phrasing as found in existing documentation.
+        * Maintain a consistent tone and style in your writing.
+        * Use proper formatting for headings, subheadings, and bullet points.
+        * Ensure that all links and references are accurate and up-to-date.
+
+        ## Continuous Improvement
+
+        We encourage feedback and continuous improvement of the documentation. If you have any suggestions or notice any issues, please open an issue or submit a pull request with your proposed changes.

.github/ISSUE_TEMPLATE/config.yml

@@ -3,3 +3,9 @@ contact_links:
   - name: Do you want to discuss EIP ideas or ask questions about the process?
     url: https://ethereum-magicians.org/
     about: Use the Fellowship of Ethereum Magicians for EIP-related discussion!
+  - name: Consistency in Style and Terminology
+    url: https://github.com/ethereum/EIPs/blob/master/.github/CONTRIBUTING.md#consistency-in-style-and-terminology
+    about: Ensure consistency in style and terminology throughout the documentation.
+  - name: Continuous Improvement
+    url: https://github.com/ethereum/EIPs/blob/master/.github/CONTRIBUTING.md#continuous-improvement
+    about: Encourage feedback and continuous improvement of the documentation.

.github/ISSUE_TEMPLATE/propose-process-change.yml

@@ -11,3 +11,19 @@ body:
       placeholder: Describe your proposed change here
     validations:
       required: true
+
+  - type: markdown
+    attributes:
+      value: |
+        ## Consistency in Style and Terminology
+
+        To ensure consistency in style and terminology throughout the documentation, please follow these guidelines:
+
+        * Use the same terminology and phrasing as found in existing documentation.
+        * Maintain a consistent tone and style in your writing.
+        * Use proper formatting for headings, subheadings, and bullet points.
+        * Ensure that all links and references are accurate and up-to-date.
+
+        ## Continuous Improvement
+
+        We encourage feedback and continuous improvement of the documentation. If you have any suggestions or notice any issues, please open an issue or submit a pull request with your proposed changes.

.github/PULL_REQUEST_TEMPLATE.md

@@ -10,3 +10,16 @@ We have a GitHub bot that automatically merges some PRs. It will merge yours imm
  - The build passes.
  - Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside <triangular brackets>.
  - If matching on email address, the email address is the one publicly listed on your GitHub profile.
+
+## Consistency in Style and Terminology
+
+To ensure consistency in style and terminology throughout the documentation, please follow these guidelines:
+
+* Use the same terminology and phrasing as found in existing documentation.
+* Maintain a consistent tone and style in your writing.
+* Use proper formatting for headings, subheadings, and bullet points.
+* Ensure that all links and references are accurate and up-to-date.
+
+## Continuous Improvement
+
+We encourage feedback and continuous improvement of the documentation. If you have any suggestions or notice any issues, please open an issue or submit a pull request with your proposed changes.

.github/workflows/auto-stagnate-bot.yml

@@ -4,21 +4,21 @@ on:
     - cron:  '0 0 * * 0'
   workflow_dispatch:
 
-name: Auto Stagnant Bot
+name: Auto Stagnate Bot
 jobs:
-  auto_merge_bot:
+  auto_stagnate_bot:
     if: github.repository == 'ethereum/eips'
     runs-on: ubuntu-latest
-    name: Auto Stagnant Bot
+    name: Auto Stagnate Bot
     steps:
       - name: Checkout
         uses: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f
       - name: Setup Node.js Environment
         uses: actions/setup-node@d98fa1113850e562f83c7fc3a89c0ecd7a87fbed
         with:
           node-version: '14'
-      - name: auto-stagnant-bot
+      - name: auto-stagnate-bot
         uses: ethereum/EIP-Bot@b3ac0ba3600aea27157fc68d1e36c08cc5a6db77 # mark-eips-stale
-        id: auto-stagnant-bot
+        id: auto-stagnate-bot
         with:
           GITHUB-TOKEN: ${{ secrets.TOKEN }}

.github/workflows/ci.yml

@@ -129,7 +129,7 @@ jobs:
           skip: .git,Gemfile.lock,**/*.png,**/*.gif,**/*.jpg,**/*.svg,.codespell-whitelist,vendor,_site,_config.yml,style.css
 
   eipw-validator:
-    name: EIP Walidator
+    name: EIP Validator
     runs-on: ubuntu-latest
 
     steps:

.vscode/launch.json

@@ -0,0 +1,65 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "command": "npm start",
+            "name": "Run npm start",
+            "request": "launch",
+            "type": "node-terminal"
+        },
+        {
+            "name": "Launch Chrome",
+            "request": "launch",
+            "type": "chrome",
+            "url": "http://localhost:8080",
+            "webRoot": "${workspaceFolder}"
+        },
+
+
+        {
+            "name": "Attach to Edge",
+            "port": 9222,
+            "request": "attach",
+            "type": "msedge",
+            "webRoot": "${workspaceFolder}"
+        },
+
+
+
+        {
+            "name": "Launch Program",
+            "program": "${workspaceFolder}/app.js",
+            "request": "launch",
+            "skipFiles": [
+                "<node_internals>/**"
+            ],
+            "type": "node"
+        },
+        {
+            "name": "Launch Program",
+            "program": "${workspaceFolder}/app.js",
+            "request": "launch",
+            "skipFiles": [
+                "<node_internals>/**"
+            ],
+            "type": "node"
+        },
+        {
+            "name": "Launch Chrome",
+            "request": "launch",
+            "type": "chrome",
+            "url": "http://localhost:8080",
+            "webRoot": "${workspaceFolder}"
+        },
+        {
+            "type": "chrome",
+            "request": "launch",
+            "name": "Launch Chrome against localhost",
+            "url": "http://localhost:8080",
+            "webRoot": "${workspaceFolder}"
+        }
+    ]
+}

Gemfile

@@ -12,7 +12,7 @@ gem "minima", "~> 2.0"
 
 # If you have any plugins, put them here!
 group :jekyll_plugins do
-  gem "github-pages", "228"
+  gem "github-pages", "229"
 end
 
 # Windows does not include zoneinfo files, so bundle the tzinfo-data gem