You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Validate LavaMoat policies on GitHub Actions rather than CircleCI.
Today we validate LavaMoat policies on CircleCI, but we update them on GitHub Actions. By migrating the validation step to GitHub Actions, we expect to speed up CI and save on CircleCI credits. Plus we'll then have all of the LavaMoat related CI steps in one place.
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
The LavaMoat policies should be validated on GitHub Actions
The LavaMoat policy validation steps should be removed from CircleCI
LavaMoat policy validation should still be a required PR status check (I.e. it should be required by the "all jobs passed" step)
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
Security
Legal
Marketing
Management (please specify)
Other (please specify)
References
No response
The text was updated successfully, but these errors were encountered:
What is this about?
Validate LavaMoat policies on GitHub Actions rather than CircleCI.
Today we validate LavaMoat policies on CircleCI, but we update them on GitHub Actions. By migrating the validation step to GitHub Actions, we expect to speed up CI and save on CircleCI credits. Plus we'll then have all of the LavaMoat related CI steps in one place.
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
Stakeholder review needed before the work gets merged
References
No response
The text was updated successfully, but these errors were encountered: