Syncthing: ignore temporary synchronization files by Aurantium-47 · Pull Request #4931 · github/gitignore · GitHub
Skip to content

Syncthing: ignore temporary synchronization files - #4931

Open
Aurantium-47 wants to merge 1 commit into
github:mainfrom
Aurantium-47:codex/syncthing-temporary-files
Open

Aurantium-47 wants to merge 1 commit into
github:mainfrom
Aurantium-47:codex/syncthing-temporary-files

Conversation

@Aurantium-47

Copy link
Copy Markdown

Link to the application or project's homepage

Syncthing

Reasons for making this change

Syncthing downloads into temporary files beside the destination file before moving them into place. These files can remain for up to a day after an interrupted transfer. The current template ignores version history, but leaves these partial downloads visible to Git.

Add the documented Unix and Windows temporary-file patterns to Global/Syncthing.gitignore. Keep the patterns specific to Syncthing rather than ignoring all .tmp files.

Links to documentation supporting these rule changes

Understanding Synchronization — Temporary Files documents .syncthing.original-filename.ext.tmp and ~syncthing~original-filename.ext.tmp, including the hash-based names used for long filenames.

Validation

Checked the original and updated templates with git check-ignore --no-index -z --stdin in isolated repositories. Eight temporary-file cases become ignored, covering both prefixes, nested paths, spaces and hash-based names. All 20 checks pass with the update; existing .stversions paths remain ignored, while ordinary files, unrelated .tmp files, .stignore and conflict copies remain visible.

Merge and Approval Steps

  • Contribution guidelines read and checked against this change.

Prepared with OpenAI Codex (gpt-6-astra, ultra reasoning, autonomous), including the patch, validation and PR description; independently reviewed by another Codex agent.

Assisted-by: OpenAI Codex (model: gpt-6-astra, autonomous)
@Aurantium-47
Aurantium-47 requested a review from a team as a code owner October 14, 2026 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant