Overriding megaignore file when adding a new sync on mega desktop

[Rashcodeacademy]

Hi,
whenever i want to add a new sync on mega desktop i write a megaignore file which is full of exclusions and put it inside the folder that i want to sync but when i add a new sync it will get overrided. you should definitely check for an existing megaignore file first or add those few lines to the existing megaignore file.
Thanks.

[mfm-mega]

Hello!

Thank you for your enquiry.

Currently, in our version 5.6.0, we do not overwrite the .megaignore file in a new sync if we detect that it already exists.
We have checked your scenario and it worked correctly:

1. We create a new local folder "TEST".
2. We manually create a .megaignore file in this new folder, and we add only one rule "-:*.txt".
3. We go to MEGA Desktop App and we create a sync between the "TEST" folder and another folder in MEGA called "TEST".
4. We check that the .megaignore still has a single rule and has not been overwritten.

Everything went correctly.
Could you tell us if this is the same case and what version you are on?

Thanks for your time.

[Rashcodeacademy]

Hello there, Thank you for your reply and the problem is still there. I am on Linux mint 21.3 which is based on Ubuntu 22.04 and i use mega desktop version 5.6.1. I also sent you a picture of about section. Best regards. [image: mega1.png]

…

On Wed, Dec 11, 2024 at 11:32 AM Mauro Ferreiro ***@***.***> wrote: Hello! Thank you for your enquiry. Currently, in our version 5.6.0, we do not overwrite the .megaignore file in a new sync if we detect that it already exists. We have checked your scenario and it worked correctly: 1. We create a new local folder "TEST". 2. We manually create a .megaignore file in this new folder, and we add only one rule "-:*.txt". 3. We go to MEGA Desktop App and we create a sync between the "TEST" folder and another folder in MEGA called "TEST". 4. We check that the .megaignore still has a single rule and has not been overwritten. Everything went correctly. Could you tell us if this is the same case and what version you are on? Thanks for your time. — Reply to this email directly, view it on GitHub <#1029 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A47TF5QPGBSGXRCX6YS5ZTL2E7WSTAVCNFSM6AAAAABTMOXBHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZUGU2TQNJYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mfm-mega]

Hello!
To continue with your case, we will need your .megaignore file and, if possible, the logs.
For security reasons, the way to proceed is to send these files to the address [email protected]. Once the email has been sent, you will receive a reply with a tracking number. Please paste this number here so that we can track the ticket.
The logs can be found at the following address: .local/share/data/Mega Limited/MEGAsync/logs.
If by any chance the logs are too big to send by email, you can do it via the app: Settings/General > Report issue. You will also receive an email with a tracking number that we need to follow up with the development team.
Thank you and have a nice day.