Comment
Git repositories with a sha256 object format appear to break the web UI by yielding a 404 HTTP response code when clicking into a particular commit from a pull request.
To demonstrate this, I've made two simple repositories:
- https://codeberg.org/dkg0/test-sha1 (uses
--object-format=sha1) - https://codeberg.org/dkg0/test-sha256 (uses
--object-format=sha256)
in each one, beyond the default main branch, i've made a branch sample-branch with a single commit, and made those branches "pull request 1" in each repo:
Clicking the "commits" tab in each of those PRs works fine:
and clicking on the actual commit itself works fine in the sha1 repo:
but yields a 404 in the sha256 repo:
### Comment
Git repositories with a sha256 object format appear to break the web UI by yielding a 404 HTTP response code when clicking into a particular commit from a pull request.
To demonstrate this, I've made two simple repositories:
- https://codeberg.org/dkg0/test-sha1 (uses `--object-format=sha1`)
- https://codeberg.org/dkg0/test-sha256 (uses `--object-format=sha256`)
in each one, beyond the default `main` branch, i've made a branch `sample-branch` with a single commit, and made those branches "pull request 1" in each repo:
- https://codeberg.org/dkg0/test-sha1/pulls/1
- https://codeberg.org/dkg0/test-sha256/pulls/1
Clicking the "commits" tab in each of those PRs works fine:
- https://codeberg.org/dkg0/test-sha1/pulls/1/commits
- https://codeberg.org/dkg0/test-sha256/pulls/1/commits
and clicking on the actual commit itself works fine in the sha1 repo:
- https://codeberg.org/dkg0/test-sha1/pulls/1/commits/80db63c77bb3eadb8b8bff31b81d5748d9076c3f
but yields a 404 in the sha256 repo:
- https://codeberg.org/dkg0/test-sha256/pulls/1/commits/205182292a6185248391c6def6500f658b54b365c4c8fde36a8546675681e459