O11Y-2148: Enable 3rd parties to view CI results

[dustinlessard-wf]

Motivation

Currently, 3rd parties cannot see the results of the CI process. This limits their ability to contribute to this codebase. Since our CI is based on Github actions, we would like to provide visibility into them. Additionally, We would like to not have to manually check that the github workflow passed and override the pipeline so we need a way to automatically check that the workflow passed and tell the pipeline that all is good.

fixes #64

Changes

-Modified the skynet.yaml so that we check that the github workflow runs and passes or fails the skynet run depending on the results.

Release Notes

Modifies the skynet.yaml so that we checks the github workflow run and passes or fails the skynet run depending on the results.

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria [outlined in CONTRIBUTING.md][contributing-manual-testing]

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A maintainer has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature

[aviary-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[semveraudit-wf]

Public API Changes

No changes to the public API found for commit eb3cfc7

Showing results for eb3cfc7

Powered by semver-audit-service. Please report any problems by filing an issue.
Reported by the dart semver audit client 2.2.2
Browse public API.