Support for integration in modern version control systems for git-ops based workflows with trestle.

[butler54]

Issue description / feature objectives

In order compliance ops on git trestle needs to have an awareness of various functionality.

Examples of desirable functionality would include:

• Support for automating approver of an SSP based on who approved a PR (or by reversed PR approvers are generated based on who is in the document).
• Integrated creation a metadata.version / metadata.version_history from git change release (e.g. oscal-semantic-version)
• automatic population of trestle metadata into models

The biggest question here is when is this worth the effort. Functionality can also be developed in a CI/ CD pipeline or scripts based on trestle.

Caveats / Assumptions

• MVP required to support Github / Github EC / Github ES
  • Ideally able to support Github / gitlab / bitbucket
• Assume that primary trestle repo SHOULD be based in the project root.
• Ability to target issue workflows at a different repository to content
• Ability to deal with pull request based workflows
• Be designed to execute within a CI pipeline (or cron job
• Support or be able to support the following CI environments (and tested with at least 2)
  • Github actions
  • Travis (and travis enterprise)
  • Jenkins
  • Tekton

Completion Criteria

• Identify and produce tests for initial use of libraries
• Setup methodology for capturing auth / config data.