git-next

History

Paul Campbell c9efbb9936 fix: ReceiveRepoConfig tries to send two messages Similar to CloneRepo the handler tries to send two messages one after the other. Leave it to WebhookRegistered handler to kick off the ValidateRepo. Also update the README with the correct message sequence.		2024-06-30 16:59:24 +01:00
..
src	fix: ReceiveRepoConfig tries to send two messages	2024-06-30 16:59:24 +01:00
Cargo.toml	refactor: extract actor-macros crate	2024-06-29 10:49:12 +01:00
README.md	fix: ReceiveRepoConfig tries to send two messages	2024-06-30 16:59:24 +01:00

README.md

stateDiagram-v2
[*] --> CloneRepo :on start

CloneRepo --> LoadConfigFromRepo :on repo config
CloneRepo --> RegisterWebhook :on server config

LoadConfigFromRepo --> ReceiveRepoConfig

ValidateRepo --> CheckCIStatus :on next ahead of main
ValidateRepo --> AdvanceNext :on dev ahead of next
ValidateRepo --> [*] :on dev == next == main
ValidateRepo --> ValidateRepo :on invalid

CheckCIStatus --> ReceiveCIStatus

ReceiveCIStatus --> AdvanceMain :on Pass
ReceiveCIStatus --> ValidateRepo :on Pending
ReceiveCIStatus --> [*] :on Fail

AdvanceNext --> ValidateRepo

ReceiveRepoConfig --> RegisterWebhook

RegisterWebhook --> WebhookRegistered

WebhookRegistered --> ValidateRepo

AdvanceMain --> LoadConfigFromRepo :on repo config
AdvanceMain --> ValidateRepo :on server config

[*] --> WebhookNotification :on push

WebhookNotification --> ValidateRepo