-
Notifications
You must be signed in to change notification settings - Fork 0
/
test_policy.yaml
94 lines (94 loc) · 3.88 KB
/
test_policy.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
# Schema: https://raw.githubusercontent.com/newrelic-forks/repolinter/master/rulesets/schema.json
version: 2
axioms: {}
rules:
readme-no-broken-links:
level: error
rule:
type: file-no-broken-links
options:
globsAll:
- README*
nocase: true
pass-external-relative-links: true
readme-file-exists:
level: error
rule:
type: file-existence
options:
globsAny:
- README*
nocase: true
fix:
type: file-create
options:
file: README.md
text:
url: https://raw.githubusercontent.com/newrelic/open-source-tools/master/nerdpacks/oss-template/README.md
policyInfo: >-
New Relic requires a README file in all projects. This README should
give a general overview of the project, and should point to additional resources
(security, contributing, etc.) where developers and users can learn further
policyUrl: https://github.com/newrelic/open-by-default
readme-contains-discuss-topic:
level: error
rule:
type: file-contents
options:
globsAll:
- README*
fail-on-non-exist: true
flags: i
content: discuss\.newrelic\.com
human-readable-content: a link to the appropriate discuss.newrelic.com topic
policyInfo: >-
New Relic recommends directly linking the your appropriate discuss.newrelic.com
topic in the README, allowing developer an alternate method of getting support
policyUrl: https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code
code-of-conduct-file-does-not-exist:
level: error
rule:
type: file-not-exists
options:
globsAll:
- CODE_OF_CONDUCT*
- CODE-OF-CONDUCT*
- CODEOFCODUCT
nocase: true
fix:
type: file-remove
options: {}
policyInfo: >-
New Relic has moved the `CODE_OF_CONDUCT` file to a [centralized location](https://github.com/newrelic/.github/blob/main/CODE_OF_CONDUCT.md)
where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other `CODE_OF_CONDUCT` file
in a repository is now redundant and should be removed
policyUrl: https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view
third-party-notices-file-exists:
level: warning
rule:
type: file-existence
options:
globsAny:
- THIRD_PARTY_NOTICES*
- THIRD-PARTY-NOTICES*
- THIRDPARTYNOTICES*
nocase: true
policyInfo: >-
A [`THIRD_PARTY_NOTICES.md`](https://github.com/newrelic/opensource-website/blob/develop/THIRD_PARTY_NOTICES.md)
file can be present in your repository to grant attribution to all dependencies
being used by this project. This document is necessary if you are using
third-party source code in your project, with the exception of code referenced outside
the project's compiled/bundled binary (ex. some Java projects require modules to
be pre-installed in the classpath, outside the project binary and therefore
outside the scope of the `THIRD_PARTY_NOTICES`). Please
review your project's dependencies and create a THIRD_PARTY_NOTICES.md file if
necessary. For JavaScript projects, you can generate this file using the
[oss-cli](https://github.com/newrelic/newrelic-oss-cli)
policyUrl: https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view
formatOptions:
disclaimer: >-
🤖*This issue was automatically generated by [repolinter-action](https://github.com/newrelic/repolinter-action),
developed by the Open Source and Developer Advocacy team at New Relic. This issue
will be automatically updated or closed when changes are pushed. If you have any
problems with this tool, please feel free to open a GitHub issue or give us a
ping in #help-opensource.*