domoscargin
domoscargin
## What Review (and document?) our build process, and ensure the team is familiar with it (perhaps through a presentation/walkthrough?) Identify areas for improvements. ## Why During a [recent incident](https://docs.google.com/document/d/1DyRYPtbRXjCvNSLu4R8wR1IxoyUjjAhRpCkio3wD-_s/edit#heading=h.p99426yo0rbv)...
## What Release a new version of GOV.UK Frontend with the latest changes we've built. ## Why So people can use this new version ## Who needs to work on...
By running `npm dedupe`
## What Our CI doesn't currently tell us if our codebase works with a new version of `lint-staged`, so we can't take for granted that major bumps will work fine,...
## What CodeQL is alerting us to the fact that we don't have explicit permissions on most of our workflows. I suspect in most cases the default is fine, but...
## Description of the issue We [build `html` renders of our nunjucks templates to diff in pull requests](https://github.com/alphagov/govuk-frontend/pull/4519). These should be ignored during publishing, but somehow our build process is,...
## What Investigate the feasibility of: - Creating GitHub Actions in [Frontend Docs](https://github.com/alphagov/govuk-frontend-docs/) and [Design System](https://github.com/alphagov/govuk-design-system/) to create a PR to bump to the latest version of govuk-frontend. - Potentially,...
## What There are some things we've identified in our test runs that need updating in the docs: - Make it clearer that a second developer should review the build...
## What Add the handle of the person who kicked off the workflow_dispatch build release to the generated PR description. ## Why While we can see who triggered a workflow...
## What Following work to [automate the building and publishing of releases](https://github.com/alphagov/govuk-frontend/issues/5580), we should extend this functionality to support branch releases. We can already release any branch we want to...