You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: practices/securing-repositories.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,16 +30,6 @@ This minimum set of requirements should be implemented alongside other relevant
30
30
- Abuse reporting must be enabled by <!-- markdown-link-check-disable -->[accepting content reports](https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository)<!-- markdown-link-check-enable -->
31
31
- In line with our [inclusive language guidance](../inclusive-language.md), the default branch must not be named "master" - we suggest "main" - please see our [inclusive language guidance](../inclusive-language.md) for how to rename the default branch.
32
32
33
-
### Repository content
34
-
35
-
- The following minimum set of files must be included in the repository, to support others to navigate the repository content:
36
-
- README.md
37
-
- CONTRIBUTING.md
38
-
- LICENSE.md
39
-
- Pull request template
40
-
- Security issue report note
41
-
- We recommend the use of a repository template, for example [NHS England Repository Template](https://github.com/nhs-england-tools/repository-template)
42
-
43
33
### Teams setup
44
34
45
35
- GitHub teams must be created to provide individuals access to repositories. The minimum recommended setup is as follows:
@@ -73,3 +63,13 @@ This minimum set of requirements should be implemented alongside other relevant
73
63
- Existing reviews must be invalidated automatically when new commits are pushed (using the `fresh-commits-invalidate-existing-reviews` option).
74
64
- Merging must be blocked if the branch is not up to date.
75
65
- Consider any further automated status checks which should be enforced prior to merging a branch
66
+
67
+
## Repository content
68
+
69
+
- The following minimum set of files must be included in the repository, to support others to navigate the repository content:
70
+
- README.md
71
+
- CONTRIBUTING.md
72
+
- LICENSE.md
73
+
- Pull request template
74
+
- Security issue report note
75
+
- We recommend the use of a repository template, for example [NHS England Repository Template](https://github.com/nhs-england-tools/repository-template)
0 commit comments