From e4e72999b291b1a5e7df2cce51dba753f2ce6bfa Mon Sep 17 00:00:00 2001
From: PSJ <51746608+thispsj@users.noreply.github.com>
Date: Mon, 2 May 2022 14:15:43 +0530
Subject: [PATCH] =?UTF-8?q?Ruby=20quickfix=20:=20Not-certified=20?=
 =?UTF-8?q?=F0=9F=92=AC=20should=20be=20at=20top?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .../building-and-testing-ruby.md                         | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 2215134058..cc894b3f85 100644
--- a/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -37,6 +37,7 @@ To get started quickly, add the starter workflow to the `.github/workflows` dire
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
+{% data reusables.actions.actions-use-sha-pinning-comment %}
 
 name: Ruby
 
@@ -100,8 +101,8 @@ Each version of Ruby specified in the `ruby-version` array creates a job that ru
 The full updated workflow with a matrix strategy could look like this:
 
 ```yaml
-{% data reusables.actions.actions-use-sha-pinning %}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
+{% data reusables.actions.actions-use-sha-pinning-comment %}
 
 name: Ruby CI
 
@@ -201,8 +202,8 @@ steps:
 The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
 
 ```yaml
-{% data reusables.actions.actions-use-sha-pinning %}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
+{% data reusables.actions.actions-use-sha-pinning-comment %}
 
 name: Matrix Testing
 
@@ -235,8 +236,8 @@ jobs:
 The following example installs `rubocop` and uses it to lint all files. For more information, see [RuboCop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
 
 ```yaml
-{% data reusables.actions.actions-use-sha-pinning %}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
+{% data reusables.actions.actions-use-sha-pinning-comment %}
 
 name: Linting
 
@@ -262,8 +263,8 @@ You can configure your workflow to publish your Ruby package to any package regi
 You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`.
 
 ```yaml
-{% data reusables.actions.actions-use-sha-pinning %}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
+{% data reusables.actions.actions-use-sha-pinning-comment %}
 
 name: Ruby Gem