brave / brave/security-action

Reports should try to tag `@brave-core-owners` whenever possible

Open
#836 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
22
Forks
8
Avg merge
2d 6h
Merged PRs (30d)
40

Description

As the description says. Notice that there is a chromium group called @brave-core-owners, and using that when for rules where only 2 members of the group occur may suffice. It can be discussed better during code review.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no file, test, or entry point. Start by locating the report-tagging logic and determine how rules with only two matching members should use @brave-core-owners; code review must settle the expected behavior, and done means reports tag that group whenever possible.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
ci-cd, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.