-
Notifications
You must be signed in to change notification settings - Fork 12
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
base: main
Are you sure you want to change the base?
ENG-256: Agree indicative content of the CONTRIBUTING.md file #57
Conversation
46ec369
to
7f08a16
Compare
caebd11
to
a6c231e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
ad42cda
to
e61dd2c
Compare
60eaff4
to
02f6e8c
Compare
02f6e8c
to
35bb407
Compare
There was a problem hiding this 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()); | ||
} | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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)) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Check terraform format ([terraform](https://developer.hashicorp.com/terraform/cli/commands/fmt)) | |
✓ Logged in as your-github-handle | ||
``` | ||
|
||
### Signing commits |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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.
35bb407
to
3c78864
Compare
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
Checklist
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.