From 7c3d1998d45ce9f0d5f85f0411a0c6313c263fb8 Mon Sep 17 00:00:00 2001
From: Eric Pyle <eric_pyle@sil.org>
Date: Fri, 6 May 2022 11:52:44 -0500
Subject: [PATCH] test workflow

---
 .github/workflows/ericpyle.yml | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 .github/workflows/ericpyle.yml

diff --git a/.github/workflows/ericpyle.yml b/.github/workflows/ericpyle.yml
new file mode 100644
index 0000000..8714e48
--- /dev/null
+++ b/.github/workflows/ericpyle.yml
@@ -0,0 +1,31 @@
+# This is your hello Github Actions file
+
+name: Hello ericpyle
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the main branch
+  pull_request:
+    branches: [ 'main' ]
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v3
+
+      # Run a single command using the runners shell
+      - name: Github json
+        run: echo '${{ toJSON(github) }}'
+# Below you can see how a second job named test could be added that runs on windows and has its own steps
+#  test:
+#    runs-on: windows-latest
+#    
+#    steps:
+      
\ No newline at end of file