From 5b850def7b29a0a855f61a52ae7be69076bd2a55 Mon Sep 17 00:00:00 2001 From: edhamiltonHO <92923571+edhamiltonHO@users.noreply.github.com> Date: Mon, 30 Oct 2023 16:46:21 +0000 Subject: [PATCH] Clarified language on move to home office platform Co-authored-by: Jeff Horton <87995501+jeff-horton-ho-sas@users.noreply.github.com> --- .../architecture-decision-records/technical-decision-log.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/technical-docs/architecture-decision-records/technical-decision-log.md b/technical-docs/architecture-decision-records/technical-decision-log.md index 61182108..baf2bc9d 100644 --- a/technical-docs/architecture-decision-records/technical-decision-log.md +++ b/technical-docs/architecture-decision-records/technical-decision-log.md @@ -6,5 +6,5 @@ | 66 | Add secret scanning to GitHub repository | GitHub provides secret scanning functionality. Users will receive alerts on GitHub for detected secrets, keys, or other tokens. Push protection can be enabled which will block commits that contain [supported secrets](https://docs.github.com/en/code-security/secret-scanning/secret-scanning-patterns#supported-secrets). These settings can be found within the settings section "Code security and analysis". | Enable "Secret scanning" with "Push protection" within repository settings. Organisation administrators, repository administrators and teams with the security manager role will receive alerts when scan detects a secret. | 2023-06-01 | None | | 65 | Add dependency vulnerability scanning using Dependabot to GitHub repository | GitHib provides dependency vulnerability scanning functionality. [Dependabot can be configured to automatically raise pull requests](https://docs.github.com/en/enterprise-cloud@latest/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates). | Dependabot configured to scan npm dependencies daily and github-actions dependencies weekly. These differ due to anticipated update cadence. | 2023-06-02 | None | | 130 | Ignore phase banner being outside landmark regions | Those elements being outside a landmark region is a moderate level failure. It is not considered to be a high priority issue by the Gov.uk design system team. See [Github issue where phase banner and landmarks is discussed](https://github.com/alphagov/govuk-frontend/issues/1604). We will revisit this decision as part of a planned review of the site design as a whole. | Axe-core has been configured to ignore elements with a `data-axe-exclude` attribute. This has been added to the phase banner and breadcrumbs. | 2023-06-16 | None | -| 72 | Moving hosting application on Home Office platform from GitHub Pages | In order to host the site under a Home Office domain (https://engineering.homeoffice.gov.uk), we are required to host the site on the Home Office platform. | Deployment actions updated to deploy to Home Office platform. | 2023-06-13 | None | +| 72 | Switch to hosting the site on a Home Office platform from GitHub Pages | In order to host the site under a Home Office domain (https://engineering.homeoffice.gov.uk), we are required to host the site on the Home Office application container platform. | Deployment actions updated to deploy to Home Office platform. | 2023-06-13 | None | | 72 | Migration of repository to [UK Home Office](https://github.com/UKHomeOffice) organisation from [HO CTO](https://github.com/HO-CTO/) | Migration of repository was required to allow hosting of application on the Home Office platform (see previous decision log item). | Migration of repository to [UK Home Office](https://github.com/UKHomeOffice/engineering-guidance-and-standards). The [previous repository location](https://github.com/HO-CTO/engineering-guidance-and-standards) has been updated to provide a redirection to the new location. | 2023-06-13 | None |