<!--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=463863) </details> <!--IssueSummary end--> <!-- Title suggestion: [Sha 256] <issue description> --> The query param `extended_sha1` on the Repository Graph is misleading when the user is working with a SHA256 repository. ## Where in the application are you seeing this issue? ### URL of the page: - https://gitlab.com/john.mcdonnell/sha256repo/-/network/main?extended_sha1=bafc1bdbd1c50915f6ac976c0749aa6f2b800584543ed670657e2dce4c35dc60 ### How did you expect the application to behave? URL Query Param should be either agnostic to SHA format, or be consistent with repository object format of the underlying project. e.g. - `/-/network/main?extended_sha256=bafc1bdbd1c50915f6ac976c0749aa6f2b800584543ed670657e2dce4c35dc60` - `/-/network/main?extended_sha=bafc1bdbd1c50915f6ac976c0749aa6f2b800584543ed670657e2dce4c35dc60` ### How did the application behave? Graph works as expected, but query params are misleading  <!-- Provide a description of how the application actually behaved -->