<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=463827) </details> <!--IssueSummary end--> <!-- Title suggestion: [Sha 256] <issue description> --> When a user creates a project using the experimental SHA256 object format, they may expect that when snippets are created in that project, that they too would default to using the same object format. See https://gitlab.com/gitlab-org/gitlab/-/issues/463828+ for similar issue relating to wikis ## Where in the application are you seeing this issue? ### URL of the page `http://gdk.test:3000/root/sha256-snippet/-/snippets` ### How did you expect the application to behave? 1. Create a project using object format SHA256 1. Navigate to `Code > Snippets` 1. Create a snippet 1. Attempt to clone the snippet repository e.g. `git clone http://gdk.test:3000/root/sha1-snippet/snippets/37.git` 1. Observe that `.git/config` shows ``` [core] repositoryformatversion = 0 [extensions] objectformat = sha256 ``` ### How did the application behave? * The application did not have any signs of error. However given that they had explicity chosen to use object format SHA256 they might expect to see their snippet repositories in said project also use SHA256