Is `.stversions` ignored by default? (Seems not for me)

Support
1

I’d be surprised if I’m the first to ask, so my apologies if this is a duplicate.

I have machine curium which does a send-only sync to machine qnap. Both machines have file versioning configured on the folder.

curium is sending the contents of its ./.stignore folder over to qnap. This doesn’t feel right? That’s its local copy of the stuff that it’s keeping due to its versioning rules.

I would have assumed that .stversions was implicitly ignored. Do I need to explicitly add it to .stignore?

  • hal6000 is the folder name.
  • This screenshot taken on qnap shows files coming over from curium

z-CleanShot 2025-10-23 08-40-55@2x
z-CleanShot 2025-10-23 08-40-55@2x1778×1188 249 KB

2

I believe I’ve answered my own question, so I’ll post it here for futurelings.

The .stignore folder that’s being synchronised is not at the root of the folder being synchronised.

It’s not ./.stignore at all, it’s ./D25 Johnny.Decimal/.stignore.

I shall exclude it manually.

3 Likes
3

For future readers, this was not about .stignore but .stversions in the first place. Otherwise the accepted answer nails it.

2 Likes