The PR Helper workflow complains if a new project doesn't include a
main_repo, so I've added that to the accepting new projects page.
I also added links from there to the specific fields in the new project
guide.
I also changed a reference in the workflow output to refer to the yaml
field name visible to submitters, rather than to the internal python
name for the same field which doesn't match.
---------
Signed-off-by: Clarence "Sparr" Risher <clrnc@amazon.com>
Co-authored-by: Holly Gong <39108850+hogo6002@users.noreply.github.com>
Update repo_url as criticality score does not support url ends with
'.git'.
Example:
~/go/bin$ `./criticality_score --format json
-gcp-project-id=clusterfuzz-external
https://github.com/kubernetes/kubernetes.git`
2023-06-21 14:27:39.583 INFO Preparing default scorer
2023-06-21 14:27:41.007 INFO deps.dev signal source enabled
`2023-06-21 14:27:41.869 WARN Repo cannot be collected {"worker": 0,
"url": "https://github.com/kubernetes/kubernetes.git", "error": "repo
failed: not found: https://github.com/kubernetes/kubernetes.git"}`
---------
Co-authored-by: Dongge Liu <alan32.liu@gmail.com>
Fix https://github.com/google/oss-fuzz/issues/10515:
1. Avoid repeated message: handle project with sub directory.
2. Simplify the email verification message
3. Link pull request without reference
1. Don't repeat criticality score for each file, only for each project.
2. Don't link to past issues to avoid notifying people unnecessarily
3. Don't @-mention people so we don't send more notifications.
Holly Gong