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

ENG-256: Agree indicative content of the CONTRIBUTING.md file #57

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

stefaniuk
Copy link
Contributor

@stefaniuk stefaniuk commented May 17, 2023

Description

Fixes #5

Context

This change is to include guidance for contributors that will work on the codebase of a repository created from this template.

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@stefaniuk stefaniuk force-pushed the ENG-256_Agree_indicative_content_of_the_CONTRIBUTING_md_file branch from 46ec369 to 7f08a16 Compare May 31, 2023 11:16
@stefaniuk stefaniuk changed the title WIP: ENG-256: Agree indicative content of the CONTRIBUTING.md file ENG-256: Agree indicative content of the CONTRIBUTING.md file May 31, 2023
@stefaniuk stefaniuk requested a review from timireland June 1, 2023 14:39
@stefaniuk stefaniuk force-pushed the ENG-256_Agree_indicative_content_of_the_CONTRIBUTING_md_file branch from caebd11 to a6c231e Compare June 7, 2023 11:44
Copy link
Contributor

@timireland timireland left a comment

Choose a reason for hiding this comment

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

Looks good

@stefaniuk stefaniuk force-pushed the ENG-256_Agree_indicative_content_of_the_CONTRIBUTING_md_file branch 2 times, most recently from ad42cda to e61dd2c Compare July 2, 2023 19:10
@stefaniuk stefaniuk force-pushed the ENG-256_Agree_indicative_content_of_the_CONTRIBUTING_md_file branch 2 times, most recently from 60eaff4 to 02f6e8c Compare July 18, 2023 18:58
@stefaniuk stefaniuk force-pushed the ENG-256_Agree_indicative_content_of_the_CONTRIBUTING_md_file branch from 02f6e8c to 35bb407 Compare July 31, 2023 14:17
Copy link
Contributor

@regularfry regularfry left a comment

Choose a reason for hiding this comment

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

We're doubling up a lot of information in here. It's probably duplication that's happened since this was written, but I suspect we're better off just with links to other places than duplicating it.

assertEquals(0, list.size());
}
```

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Note that the `// Arrange`, `// Act`, and `// Assert` comments are not required. They are presented here to highlight the structure.

I've seen all sorts of projects where people seem to have got the idea that they need these comments in every test, might as well clarify it.

}
```

### Code review
Copy link
Contributor

Choose a reason for hiding this comment

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

It might well not have done so when it was written, but this section seems to double up with https://github.com/NHSDigital/software-engineering-quality-framework/blob/340f9bfc64e4c8ac5ebcbc4d87d5fc2c76e37490/patterns/everything-as-code.md?plain=1#L43; we should only have this guidance in one place, really.


### Pull Request

- Set the title to `REF-XXX: Descriptive branch name`, where `REF-XXX` is the ticket reference number
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we have a definitive board (Jira or otherwise) that we should be taking ticket references from? Do we need one?

- Check file format ([EditorConfig](https://github.com/editorconfig))
- Check markdown format ([markdownlint](https://github.com/DavidAnson/markdownlint))
- Scan secrets ([GitLeaks](https://github.com/gitleaks/gitleaks))

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Check terraform format ([terraform](https://developer.hashicorp.com/terraform/cli/commands/fmt))

✓ Logged in as your-github-handle
```

### Signing commits
Copy link
Contributor

Choose a reason for hiding this comment

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

We should remove this section in favour of the commit signing docs


## Local environment

### Prerequisites
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this is now covered by the README.


To ensure all the prerequisites are installed and configured correctly, please follow the [nhs-england-tools/dotfiles](https://github.com/nhs-england-tools/dotfiles) installation process.

### Development environment configuration
Copy link
Contributor

Choose a reason for hiding this comment

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

As is this.


## Git and GitHub

### Configuration
Copy link
Contributor

Choose a reason for hiding this comment

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

This is covered in the dotfiles repository.


More information on the git settings can be found in the [Git Reference documentation](https://git-scm.com/docs).

### Authentication
Copy link
Contributor

Choose a reason for hiding this comment

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

Feels like this ought to be somewhere else, but I'm not sure where.

@stefaniuk stefaniuk force-pushed the ENG-256_Agree_indicative_content_of_the_CONTRIBUTING_md_file branch from 35bb407 to 3c78864 Compare November 25, 2023 08:17
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.

ENG-256: Agree indicative content of the CONTRIBUTING.md file
3 participants