From cb395a0653d12efe2080b983caa86f7bf5b6d545 Mon Sep 17 00:00:00 2001
From: Nick Fields <46869826+nick-fields@users.noreply.github.com>
Date: Tue, 15 Feb 2022 21:20:58 -0500
Subject: [PATCH] Update README.md to reflect ownership change

---
 README.md | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 91cb155..a328350 100644
--- a/README.md
+++ b/README.md
@@ -4,6 +4,8 @@
 
 Allows data to be shared between jobs and accessed via env variables and step output
 
+**NOTE:** Ownership of this project was transferred to my personal account `nick-fields` from my work account `nick-invision`.  Details [here](#Ownership)
+
 ---
 
 ## **Inputs**
@@ -27,7 +29,7 @@ Allows data to be shared between jobs and accessed via env variables and step ou
 ### Example storing data
 
 ```yaml
-- uses: nick-invision/persist-action-data@v1
+- uses: nick-fields/persist-action-data@v1
   with:
     data: ${{ steps.some-step.output.some-output }}
     variable: SOME_STEP_OUTPUT
@@ -36,7 +38,7 @@ Allows data to be shared between jobs and accessed via env variables and step ou
 ### Example using data from another job via env variable
 
 ```yaml
-- uses: nick-invision/persist-action-data@v1
+- uses: nick-fields/persist-action-data@v1
   with:
     data: ${{ steps.some-step.output.some-output }}
     retrieve_variables: SOME_STEP_OUTPUT, SOME_OTHER_STEP_OUTPUT
@@ -46,10 +48,19 @@ Allows data to be shared between jobs and accessed via env variables and step ou
 ### Example using data from another job via output
 
 ```yaml
-- uses: nick-invision/persist-action-data@v1
+- uses: nick-fields/persist-action-data@v1
   id: global-data
   with:
     data: ${{ steps.some-step.output.some-output }}
     retrieve_variables: SOME_STEP_OUTPUT, SOME_OTHER_STEP_OUTPUT
 - run: echo ${{ steps.global-data.outputs.SOME_STEP_OUTPUT }}
 ```
+
+
+---
+
+## **Ownership**
+
+As of 2022/02/15 ownership of this project has been transferred to my personal account `nick-fields` from my work account `nick-invision` due to me leaving InVision.  I am the author and have been the primary maintainer since day one and will continue to maintain this as needed.
+
+No immediate action is required if you rely on this as GitHub handles ownership transfers pretty well. Any current workflow reference to `nick-invision/persist-action-data@<whatever>` will still work, but will just pull from `nick-fields/persist-action-data@<whatever>` instead.  Who knows how long that will work, so at some point it would be beneficial to update your workflows to reflect the new owner accordingly.