Classic confinement request for git-spice

store-requests classic-confinement
1

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

  • name: git-spice
  • description: Tool for managing stacked branches and pull requests.
  • snapcraft: snapcraft generated from goreleaser configuration: git-spice/.goreleaser.yml at dc8e11626641dc179c8347c9ed01a50ed7e986ce · abhinav/git-spice · GitHub
  • upstream: GitHub - abhinav/git-spice: Manage stacked Git branches · GitHub
  • upstream-relation: author
  • supported-category: tools for local, non-root user driven configuration of/switching to development workspaces/environments
  • reasoning: git-spice is a dev tool. It manages branch stacks in arbitrary Git repositories and must invoke the user’s normal Git tooling and authentication environment. It pushes branches on their behalf using git push, so Git needs access to their SSH configuration as well. State for git-spice is stored per-repo inside that repository’s Git object store itself.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

2

This request has been added to the queue for review by the @reviewers team.

3

Hey @abhg

must invoke the user’s normal Git tooling and authentication environment.

This reason is unsupported as per the Process for reviewing classic confinement snaps (Dependent software only available on host). You should ship git binary inside the snap (eg, stage-packages, build from source)

Git needs access to their SSH configuration as well.

This cab be done via ssh-keys interface

Thanks