Update repos that have moved to GitHub

The Chef repo is still on GitLab, otherwise repos
have moved to GitHub.

src/govpress-unit/plugin-reviews.md

@@ -13,7 +13,7 @@ below):
 1. Check for existing inspections
 2. Add a card to the Trello board
 3. Check the plugin for issues using
-   [pluginscan](https://git.govpress.com/dxw/pluginscan)
+   [pluginscan](https://github.com/dxw/pluginscan)
 4. Check for incompatibilities with our [hosting platform](https://github.com/dxw/govpress-technical-docs/blob/main/software-development/add-a-new-plugin.md)
 5. Write up an inspection report in advisories.dxw.com. If the plugin does not
    appear to be vulnerable, this can be published immediately
@@ -60,7 +60,7 @@ Most plugins can be downloaded from the
 [directory](https://en-gb.wordpress.org/plugins/). Premium plugins may have to
 be purchased (discuss with DMs).
 
-We use a tool called [Pluginscan](https://git.govpress.com/dxw/pluginscan) for
+We use a tool called [Pluginscan](https://github.com/dxw/pluginscan) for
 inspections. It does not have a full understanding of the code - instead it
 looks for specific patterns and function names which may indicate that the code
 is unsafe.

src/govpress-unit/support.md

@@ -117,22 +117,22 @@ These are the systems you will need access to:
   and assign it to the 1st line support group where it will be picked up by
   colleagues in Technical Operations).
 - The v1 GovPress infrastructure (follow the docs
-  [here](https://git.govpress.com/ops/docs/-/blob/master/create-a-user-data-bag-for-chef.md)
+  [here](https://github.com/dxw/ops-docs/blob/master/create-a-user-data-bag-for-chef.md)
   and raise an MR).
 - Our old "Helpful" infrastructure (ask someone from the Maintenance and Support
   Team to help).
 - Basic auth, which we use for access to the GovPress v1 staging sites (follow
   the docs
-  [here](https://git.govpress.com/ops/docs/-/blob/master/create-a-user-data-bag-for-chef.md)
+  [here](https://github.com/ops-docs/blob/master/create-a-user-data-bag-for-chef.md)
   and raise an MR).
 - The dxw VPN (follow the docs
-  [here](https://git.govpress.com/ops/docs/-/blob/master/create-a-user-data-bag-for-chef.md)
+  [here](https://github.com/ops-docs/blob/master/create-a-user-data-bag-for-chef.md)
   and raise an MR).
 - Papertrail for Dalmatian infrastructure application logs (ask someone from
   the Maintenance and Support Team to help).
 
 The documentation
-[here](https://git.govpress.com/ops/docs/-/blob/master/create-a-user-data-bag-for-chef.md)
+[here](https://github.com/ops-docs/blob/master/create-a-user-data-bag-for-chef.md)
 describes how to actually access a running server or instance. If you need to
 find the highest id in the current user data bags, you can run:
 
@@ -153,7 +153,7 @@ Please ensure that you have the following installed before your start your rotat
 put the main script on your $PATH)
 
 And make sure you have the [`govpress-developer-docs`](https://github.com/dxw/govpress-developer-docs)
-repo and [`ops/docs` repo](https://git.govpress.com/ops/docs/) bookmarked, along
+repo and [`ops/docs` repo](https://github.com/ops-docs/) bookmarked, along
 with the [Project Knowledgebase on AirTable](https://airtable.com/appL5dzrJCzmldhcG/tbllUuMjfRR8Npe61/viwsS1RB8nJZjBekX?blocks=hide).
 
 Please also ensure that you have the [incident.io](https://incident.io/) app

src/tech/dealing-with-an-incident.md

@@ -104,7 +104,7 @@ always good steps:
   the impact of this event (looking at logs, metrics etc.)
 
 Once you have identified the problem see if there is an
-[Ops Docs](https://git.govpress.com/ops/docs) guide for this error.
+[Ops Docs](https://github.com/ops-docs) guide for this error.
 
 ### Declaring an incident
 
@@ -475,4 +475,4 @@ Any actions should be added to the  follow up actions of the Incident in
 incident.io and given an owner. The owner should add the action to any relevant
 trello board and ensure the work is done in a timely manner. If the action has
 impact on the ISMS it should be added to the Findings tracker and ISMS trello
-board as well.
+board as well.

src/tech/getting-a-project-ready-for-support.md

@@ -63,7 +63,7 @@ to add, please ask in Slack.
 ## Add the project to the operations documentation
 
 Make sure the client has a document in the
-[operations documentation](https://git.govpress.com/ops/docs) repository. It
+[operations documentation](https://github.com/ops-docs) repository. It
 should include either documentation or (preferably) links to documentation for
 any on-boarding steps needed, and the front line support runbook.
 

src/tech/support-and-on-call.md

@@ -28,7 +28,7 @@ Being on call means you are the first line support for issues that occur out of
 
 While on call, your responsibility is making sure all the services we support are running correctly and effectively.
 
-As with in-hours support, we use monitoring and alerts to notify you when an issue occurs via Opsgenie, and provide [runbooks](https://git.govpress.com/ops/docs) to help you respond to those issues. The difference to in-hours support is that you’ll only be alerted when a high-severity issue occurs, and you aren’t expected to take any action out of hours unless alerted.
+As with in-hours support, we use monitoring and alerts to notify you when an issue occurs via Opsgenie, and provide [runbooks](https://github.com/ops-docs) to help you respond to those issues. The difference to in-hours support is that you’ll only be alerted when a high-severity issue occurs, and you aren’t expected to take any action out of hours unless alerted.
 
 Outside office hours, the expected response depends on the severity of the incident. We have a set of factors that determine the severity of an incident, and have included these in our [Service Level Agreement](https://contracts.dxw.com/service_level_agreement.md).