Also analyze revisions that are not public.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 52
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 54
Description
If the revision has a custom policy, hence is not public, code-review will not scan it. This primarily happens on two scenarios:
- Revision is tight to a bugzilla item that is sec issue
- Revision is not bonded to any bugzilla issues, like https://phabricator.services.mozilla.com/D154070
This should be addressed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how code-review selects revisions for scanning and how custom policies make revisions non-public. Compare that path with the public-revision path and use Phabricator revision D154070 as an example. Done means revisions tied to security Bugzilla items or to no Bugzilla issue are also analyzed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100