ci/cd Pipeline checks for documentation being merged

[5byuri]

IDEA, POC

THIS IS A STANDALONE CI/CD Repository, this is to show how easy it is to do

To ensure a well documented project in the future, we need to force new features to be added to the devguard-documentation.

We could have a CI/CD Pipeline check if a branch with the same name in the documentation has already been merged, else it will fail.

A Witness produces a json that logs certain information in the build process. Program a cli tool that creates a json. This can then be used for compliance and to proof that for example documentation has been properly written and merged before deploying

You are just a Witness not a Judge. Generally give data, dont check just for label === bug but just return every label, so its scalable. The Judge would be a Rego Policy, so that any Company can be a Judge. https://docs.github.com/en/actions/reference/workflows-and-actions/variables

Branch -> Ticket-name

tba

• [ ]
• [ ]
• [ ]
• [ ]

Witness.dev