Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add code review in GovPress page #1193

Merged
merged 1 commit into from
Aug 22, 2023
Merged

Add code review in GovPress page #1193

merged 1 commit into from
Aug 22, 2023

Conversation

snim2
Copy link
Contributor

@snim2 snim2 commented Aug 22, 2023

This page describes some details in the GovPress code review workflow that are slightly different to the general Tech Team workflow, or where we feel it is important to emphasise particular practices.

@netlify
Copy link

netlify bot commented Aug 22, 2023

Deploy Preview for laughing-payne-b9fbd2 ready!

Name Link
🔨 Latest commit 0d4b881
🔍 Latest deploy log https://app.netlify.com/sites/laughing-payne-b9fbd2/deploys/64e49e281d676b00083e5546
😎 Deploy Preview https://deploy-preview-1193--laughing-payne-b9fbd2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@snim2 snim2 marked this pull request as ready for review August 22, 2023 10:20
src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
---


GovPress follows [the same process for software development](https://playbook.dxw.com/tech/how-we-do-development/) as the Tech Team. However, developers in the Tech Team work on a small number of long-running projects, with relatively large teams. In GovPress we work on a very large number of small projects, with small teams, so we have a slightly different emphasis on how we write code.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

relatively large teams - well, large (~8-15) if you include other dxw discplines, but not usually more than three devs on a project 😅

src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
src/govpress-unit/code-review.md Outdated Show resolved Hide resolved

All developers are expected to undertake code review. Unless a PR only includes documentation, or similar, you should _always_ test the changeset locally. If it is not clear how to do this, ask the PR author using the **Request changes** feature in GitHub, or similar.

PRs should not be held up unnecessarily, so if you have questions about the changeset, or small requests, be clear to tell the author if your comments are non-blocking. Your main role is to prevent bugs appearing on live systems, and to minimise the amount of technical debt in our repositories. If your suggested changes do not achieve either of those aims, they should not block a merge.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PRs should not be held up unnecessarily, so if you have questions about the changeset, or small requests, be clear to tell the author if your comments are non-blocking. Your main role is to prevent bugs appearing on live systems, and to minimise the amount of technical debt in our repositories. If your suggested changes do not achieve either of those aims, they should not block a merge.

Feels relevant in the general tech team guidance too

src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
src/govpress-unit/code-review.md Show resolved Hide resolved
src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
Copy link
Contributor

@yndajas yndajas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple more in addition to the above

src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
Copy link
Contributor

@RobjS RobjS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a really good summary of the way we should be working 👍 Thanks!

src/govpress-unit/code-review.md Outdated Show resolved Hide resolved
@snim2
Copy link
Contributor Author

snim2 commented Aug 22, 2023

Thanks folks, this has been a very good example of code review working well :) I'll squash these commits before merge

This page describes some details in the GovPress code review
workflow that are slightly different to the general Tech
Team workflow, or where we feel it is important to
emphasise particular practices.
@snim2 snim2 force-pushed the feature/govpress-code-review branch from ed45885 to 0d4b881 Compare August 22, 2023 11:38
@snim2 snim2 merged commit 17109de into main Aug 22, 2023
6 checks passed
@snim2 snim2 deleted the feature/govpress-code-review branch August 22, 2023 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants