package crs
A tool for managing code review comments embedded in source code
Install
dune-project
Dependency
Authors
Maintainers
Sources
crs-0.0.20250914.tbz
sha256=dad0c46a83ef40da150d8b840b01c66af3b979dfa7c3e17c3edef38aa84b804f
sha512=d7a8b2a34f4a3ddda0eaaa3e4248ec2870f944a5d64782bd73b031637b01e94a378d7534b1c02da739f32343b342ed8e8bf491e6442a3bd7b0e748bd61c58770
doc/crs.crs-cli/Crs_cli/Private/Review_mode/index.html
Module Private.Review_mode
Source
Review_mode.t
describes the context in which the CR assignment and annotation logic is executed. This is not strictly tied to the CI event that triggered the workflow, but rather to the review/assignment semantics:
Pull_request
: The workflow is running in the context of a pull request, and theauthor
is the user who opened the PR. We are in the process of requiring thebase
revision of the PR, but currently are supporting older workflow that do not supply it. We expect the base to be supplied by the most up to date clients.
Revision
: The workflow is running in the vcs tree checked out at a specific revision and there is no specific PR.
There exists a natural mapping between the event kinds that are triggering GitHub Actions Workflows and this review mode. Namely:
github.event_name == 'pull_request'
: This is a pull request event and maps to thePull_request
review mode.
github.event_name == 'push'
: Jobs triggered on a'push'
event are best run inRevision
review mode. In this mode, workflows run in the tree checked out at a specific revision, but the context is not tied to a particular pull request.
Build a t
from parsing arguments in the command line. For convenience and help users discover warnings during CI runs, this can optionally include CI warnings on stderr for GitHub, using workflow annotations. To activate, supply emit_github_annotations:true
.
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>