yfprojects

Borg goes through the pattern file from top to bottom. With `var/snap/plexmediaserver/common/Library/Application Support/Plex Media Server` it first hits the rule to include that path so it doesn't look any further...

> Github only supports allowing editing either to everyone or to users with push access. ~~But I don't have push access, do I?~~ > What harm can be done --...

That's reasonable enough. There are no further objections on my part. Though this policy could be stated somewhere in the Wiki to avoid future confusion.

> I think the Contribution guide would be more appropriate. Yes, that would be a suitable place. However adding a statement to the plugin page in the Wiki on how...

Looking good! When changing the path of the repo, the user can enter a path to any repo. How would vorta handle this?

So why do we need this then if it behaves exactly like adding an existing repo?

> Makes sense. What about extra borg argument field? We already have an entry for extra arguments that only applies to `create`. These two should be grouped together I think.

> @real-yfprojects Sorry not sure what you are referring to. Can you point me to code? https://github.com/borgbase/vorta/blob/1f1278270df5dd452ffaa3646912f2520387a9c7/src/vorta/views/schedule_tab.py#L84-L86

Since repositories aren't assigned a specific profile but can be used in multiple or none at all, I suggest adding a tab to the settings view listing all the repositories...

> Maybe we can display `Compression Size: Calculating` till the version is known and then populate/hide it accordingly? I like that.