Median Task: TRP-51
the plan for tripwire:
condense everything down to: workflows, home, rules, insights
home = high level summary of repo activity, with charts and shit.
workflows = node based editor composing of rules with set triggers and actions
rules = single set boolean requirements ALL users of the repo must follow (besides people belonging to the org, maintainers, etc)
our focus is creating an MVP and making the core for GitHub.
once mvp is finalized, we can focus on making tripwire agnostic to git as a whole.
review structure:
github review comment as CONDENSE as possible with a button leading to the particular workflow run responsible for that pr. each workflow has its own run, but if multiple workflows are present for prs, join the workflows into 1 run and present one singular button on the pr that links back to that run on the dashboard.
rules:
make their primitives result on the server as json, but each rule should be composed as a type in the code so we can expose to an sdk later on.
Median Task: TRP-51
the plan for tripwire:
condense everything down to: workflows, home, rules, insights
home = high level summary of repo activity, with charts and shit.
workflows = node based editor composing of rules with set triggers and actions
rules = single set boolean requirements ALL users of the repo must follow (besides people belonging to the org, maintainers, etc)
our focus is creating an MVP and making the core for GitHub.
once mvp is finalized, we can focus on making tripwire agnostic to git as a whole.
review structure:
github review comment as CONDENSE as possible with a button leading to the particular workflow run responsible for that pr. each workflow has its own run, but if multiple workflows are present for prs, join the workflows into 1 run and present one singular button on the pr that links back to that run on the dashboard.
rules:
make their primitives result on the server as json, but each rule should be composed as a type in the code so we can expose to an sdk later on.