Requesting approval to use classic confinement for Uplift snap

I have created an application called Uplift that can perform automated semantic versioning based on the Conventional Commits used within commit messages.

For this application to work, it needs to modify files within a users repository and push changes back to a remote using the Git client. From reading the documentation, I understand that I need to request classic confinement.

Please let me know if there is anything I need to do.

Hey @ga-paul-t,

So if uplift needs to modify files within a users repository, it should be enough to plug some interfaces that can provide write access to typical locations where users store code repositories, like home, personal-files or even system-files.

Which are the exact issues that are preventing uplif to run under strict confinement?

Thanks!

@emitorino thanks for coming back to me. I will take a look

@emitorino this could be a lack of understanding on my part of how snap works. This is the first time I have used it. I have looked at those interfaces and it seems they would provide exactly what I need. Ultimately uplift needs access to git as it will manage tags and push changes back to a remote. It also needs access to wherever the user clones their repository, which I imagine will typically be their home folder.

I guess this is achievable under strict confinement? But it feels like auto-connecting those interfaces are required? Can a snap invoke other applications like git? Or would you have to explicitly specify paths it can access?