Closed krancour closed 6 months ago
Name | Link |
---|---|
Latest commit | b70c46a32c0b7875206586e71b5cf4096e872bf9 |
Latest deploy log | https://app.netlify.com/sites/docs-kargo-render-akuity-io/deploys/6601cefa450f040007138c1c |
Deploy Preview | https://deploy-preview-268.bookkeeper.akuity.io |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Attention: Patch coverage is 53.84615%
with 6 lines
in your changes are missing coverage. Please review.
Project coverage is 27.72%. Comparing base (
89fd5f9
) to head (b70c46a
).
Files | Patch % | Lines |
---|---|---|
branches.go | 62.50% | 2 Missing and 1 partial :warning: |
service.go | 0.00% | 2 Missing :warning: |
rendering.go | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
When we write to a stage-specific branch, we gut its existing contents entirely and render into the empty directory. The long-time exception to that has been that we do not delete any files or directories explicitly named in the Kargo Render config as
preservedPaths
.Only if writing to a local directory instead of a remote branch, all files that were meant to be preserved are going missing. The reason is that we have been rendering into a brand new, empty directory, when really, we should have been copying whatever was to be preserved from the target branch.
Note that since I worked on a new test case that involved a temporary directory, I have also taken the liberty of fixing a few outstanding temp directory-related nits.