sync: protect build uploads and credential-bearing files - #26
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remote builds could upload Git-ignored deployment overlays containing credentials. Source uploads now use one Git-aware file selection for transfer and provenance, with explicit build-artifact includes, protected secret/config paths, and private attempt directories. Static uploads also exclude protected paths; doctor reports historical exposure without changing files.
Syncs the complete Forgejo main tree at 671fb99. Validation: full Go tests, vet and build; repository-context checks for Ship, Dash and Observe.