From 718770750470a9a24928437340f66185fb75d18b Mon Sep 17 00:00:00 2001 From: lbadenhop Date: Fri, 13 Sep 2024 08:52:58 -0700 Subject: [PATCH 1/2] Update README.md Remove reference to Netlify. This is no longer used. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1c13182d..1fcadef9 100644 --- a/README.md +++ b/README.md @@ -141,7 +141,7 @@ The outline process is as follows: * The relevant subject matter expert creates a new branch and starts work on their changes. * When they are happy they commit and push to the branch. * They then create a Pull Request, which creates a Preview site that can reviewed on Netlify (link to the site is shown in the Pull Request page). The technical writer then reviews and suggest changes, etc. -* When approved the changes are merged to `master`. This kicks off a deployment in Netlify to the [Netlify site](https://axway-open-banking-docs.netlify.app/). +* When approved the changes are merged to `master`. * The final step is a merge to production, which does not necessarily need to be performed at each merge to `master` on GitHub. This happens through a manual push to Zoomin, the production provider for https://docs.axway.com. -Production is handled by the technical writer assigned to the project. \ No newline at end of file +Production is handled by the technical writer assigned to the project. From 4a4a2d558b481efa05b27a4f932b7227acb18d82 Mon Sep 17 00:00:00 2001 From: lbadenhop Date: Fri, 13 Sep 2024 08:57:20 -0700 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1fcadef9..76850215 100644 --- a/README.md +++ b/README.md @@ -140,7 +140,7 @@ The outline process is as follows: * The relevant subject matter expert creates a new branch and starts work on their changes. * When they are happy they commit and push to the branch. -* They then create a Pull Request, which creates a Preview site that can reviewed on Netlify (link to the site is shown in the Pull Request page). The technical writer then reviews and suggest changes, etc. +* They then create a Pull Request. The technical writer then reviews and suggest changes, etc. * When approved the changes are merged to `master`. * The final step is a merge to production, which does not necessarily need to be performed at each merge to `master` on GitHub. This happens through a manual push to Zoomin, the production provider for https://docs.axway.com.