Implement basic CI/CD

[sergmetelin]

Requirements
As a user of the Guardian, prior to publishing a Policy Workflow Execution Instance, I would like to validate requirements such as schemas, tokens, etc. If there is an issue, I will need to know what requirement the issue is related to and how to fix it.

Pre-requisite
Information Architecture Diagrams? BRD's? FSD's for this Enhancement / Feature?

Definition of Done
The CI should cover linting as well as unit tests at a minimum.

Acceptance Criteria:
The CI should cover linting as well as unit tests at a minimum.

[sergmetelin]

I guess another config is to limit merges to the main branch and all changes by default to be merged in develop? (depending on your branching strategy)

[blockchain-biopharma]

This is another Duplicate of Issue 40. Closing with a Link:

https://app.zenhub.com/workspaces/guardian-618c27c08661c0001461263a/issues/hashgraph/guardian/40

[anvabr]

Note: Reopened the issue and changed its focus on implementation of the CI (budges are covered in the #40).

Requirements

CI/CD is a common 'best practice' to organising software development. This ticket requires the implementation of Github Actions workflow to be triggered every time a commit to main has occurred.

DOD

The workflow described in the Acceptance Criteria section below is executed automatically triggered by the change in the main repo.

Acceptance Criteria

Github Actions workflow exists in the /.github/workflows/ci.yml containing the following logic which gets executed on every commit to MAIN:

• Codebase is "linted", i.e. checked and formatted by the lint utility
• Repo is tagged
• Software artefacts are built and published (where appropriate)
• Unit tests are executed and the results are recorded

[blockchain-biopharma]

@danielnorkin @sergmetelin This was just QA Tested and complete, moving to Close.