- When the repository is initalized with a different objectformat than sha1, ensure that the empty repository instructions reflects that the
git initcommand also needs to be initialized with that objectformat. - Resolves Codeberg/Community#1837
- Added integration test.
fix: use correct init instruction for sha256 #7394
-
added the forgejo/uibugconfirmedtestpresentbackport/v11.0/forgejolabels
- requested reviews from caesar, crystal, 0ko
Needs lint fixing
@ -51,3 +51,3 @@
<div class="markup">
<pre><code>touch README.md
git init
git init{{if eq .Repository.ObjectFormatName "sha256"}} --object-format=sha256{{end}}
There's also the "Pushing an existing repository from the command line" part which may need some update to reflect that it's not possible to push a sha1 local repo to a sha256 remote repo. But it's fine without.
User going through the trouble of creating a remote sha256 repo should be acknowledging the incompatibility.
I think Git will already take care of that message when pushing. Although that statement might become false with a future Git version and might handle it transparently.
It was not easy to recall where these instructions are but they are sure useful to a few people and not harmful.
The change is good.
4429a70987
485a16a2b3
The backport to v11.0/forgejo failed. Check the latest run for more details.
Archived
Scheduled for backport to Forgejo v1.19
Archived
Scheduled for backport to Forgejo v1.20
Archived
Scheduled for backport to Forgejo v1.21
Archived
Automated backport to v10.0
Archived
Automated backport to v11.0
Automated backport to v12.0
Archived
Automated backport to v13.0
Archived
Automated backport to v14.0
Scheduled for backport to Forgejo v7.0
Archived
Scheduled for backport to Forgejo v8.0
Archived
Scheduled for backport to Forgejo v9.0
Archived
The release containing this change is not backward compatible
Something is not working
Archived
it can be reproduced
bug has already been reported in the Forgejo tracker
the information provided does not contain enough details
bug has just been reported and need triage (default label on issue creation)
bug cannot be fixed within Forgejo easily, it has been reported upstream
Forgejo Actions feature
API
Forgejo Authentication
Forgejo as Identity Provider (in OAuth/OIDC flow)
Forgejo as Relying Party / Client (in OAuth/OIDC flow)
Everything related to email in Forgejo
Federation
Related to the Git backend in Forgejo
Migration between Git forges (i.e. for GitHub, GitLab, Gitea, Forgejo, etc.). NOT for database migrations.
Forgejo package and container registry
https://www.mysql.com/
https://www.postgresql.org/
https://sqlite.org/
https://codeberg.org/forgejo/forgejo/issues/2779
github.com/caddyserver/certmagic
Archived
https://github.com/chartjs/Chart.js
Archived
https://github.com/go-chi/chi/
Archived
https://github.com/alecthomas/chroma/
Archived
https://github.com/larsgw/citation.js/
Archived
https://github.com/codespell-project/codespell
Archived
https://github.com/webpack-contrib/css-loader
Archived
https://github.com/devcontainers/cli
Archived
https://github.com/dropzone/dropzone
Archived
https://github.com/editorconfig-checker/editorconfig-checker
Archived
https://www.elastic.co/elasticsearch
Archived
https://github.com/jhillyerd/enmime
Archived
https://f3.forgefriends.org/
https://forgefed.org
https://git.deuxfleurs.fr/Deuxfleurs/garage
https://git-scm.com/
Archived
https://github.com/kiegroup/git-backporting
Archived
https://github.com/go-gitea/gitea
https://github.com/github/gitignore
Archived
https://github.com/go-ap/activitypub
Archived
https://github.com/go-enry/go-enry
Archived
https://github.com/xanzy/go-gitlab
Archived
https://github.com/niklasfasching/go-org
Archived
https://github.com/sassoftware/go-rpmutils
Archived
https://github.com/go-sql-driver/mysql/
Archived
github.com/go-swagger/go-swagger
Archived
https://github.com/hashicorp/go-version
Archived
https://github.com/go-webauthn/webauthn
Archived
https://github.com/go-co-op/gocron
Archived
https://go.dev/
https://github.com/yuin/goldmark
Archived
github.com/PuerkitoBio/goquery
Archived
https://github.com/markbates/goth/
Archived
https://github.com/grpc/grpc-go
Archived
https://github.com/capricorn86/happy-dom
Archived
https://helm.sh/
Archived
https://github.com/opencontainers/image-spec
Archived
https://github.com/santhosh-tekuri/jsonschema
Archived
https://github.com/KaTeX/KaTeX
Archived
All linting tools and libraries
Archived
https://mariadb.com/
Archived
https://github.com/mermaid-js/mermaid/
Archived
https://github.com/minio/minio-go/
Archived
github.com/golangci/misspell/cmd/misspell
Archived
https://github.com/microsoft/monaco-editor
Archived
https://pdfobject.com/
Archived
https://playwright.dev/
Archived
https://github.com/postcss/postcss
Archived
https://github.com/csstools/postcss-plugins
Archived
https://github.com/google/pprof
Archived
https://github.com/prometheus/client_golang
Archived
https://google.golang.org/protobuf
Archived
https://github.com/github/relative-time-element
Archived
https://github.com/renovatebot/renovate
Archived
https://code.forgejo.org/forgejo/reply
Archived
https://github.com/gliderlabs/ssh
Archived
https://github.com/swagger-api/swagger-ui
Archived
https://tailwindcss.com/
Archived
https://github.com/fullcalendar/temporal-polyfill
Archived
github.com/buildkite/terminal-to-html
Archived
Undifferentiated dependencies used for testing only
Archived
https://github.com/github/text-expander-element
Archived
https://github.com/urfave/cli
Archived
https://github.com/lunny/vfsgen
Archived
https://vitejs.dev/
Archived
https://woodpecker-ci.org/
Archived
https://golang.org/x/tools
Archived
https://gitea.com/xorm/xorm
Archived
This issue or pull request already exists
New feature
Accessibility (a11y)
Branding (logo, name, tagline etc.)
Forgejo Actions CI configuration
The commit graph feature and page.
Keeping Forgejo in sync with its dependencies and contributing back to them
Archived
t9n/translation, l10n/localization, and i18n/internationalization of Forgejo
Interoperability with other services: Webhooks, bridges, integrations
Moderation
Privacy first
Release management
Performance and scaling
Security (please disclose responsibly)
User interface
User research provides indicators that this would be good to have, interested contributors are encouraged to pick this.
This is likely worth having, but the assumption is not backed by user research data (it might benefit a small amount of users only.) Unlikely to receive much attention, but feel free to pick.
Not enough information to assess the request's benefits. This issue may be closed if no gain is established: You can help by giving us more input.
User research indicates that this is an important improvement for Forgejo users. Contributions very welcome!
Optimal for first-timers! Make sure to look for further explanations and ask for help if needed. If you want, you can consider the person who added this label as a point of contact.
This PR needs to be backported to stable branch of Forgejo safely and manually, using a migration script.
Large impact: Potential data loss, many users affected, major degradation in UX.
Medium impact: Several users affected, degradation in UX, workarounds might be available but inconvenient.
Small impact: No data loss, workarounds might be available, affects few users.
Report was not yet triaged to assess impact.
This pull request contains changes that are not (yet) compatible with the current Forgejo license
The issue was resolved in the repository of the dependency
An issue should be created in the respository of the dependency
An open issue exists in the upstream repository of the dependency
Pull requests that have been merged with a manual test
Archived
The manual test instructions were followed
Specific to the FreeBSD Operating System
Specific to (GNU/)Linux Operating Systems
Specific to the MacOS Operating System
Specific to the Windows Operating System
A user report about a problem. Needs to be triaged to find potential solutions.
found in the version of the milestone and not before
Issues that must be fixed before the release can be published
Only bug fixes with automated tests (except for CSS/JavaScript)
Issues that must be fixed before Forgejo v7.0 can be released 17 April 2024
Archived
Issues that must be fixed before Forgejo v7.0.1 can be released
Archived
Issues that must be fixed before Forgejo v7.0.2 can be released
Archived
Issues that must be fixed before Forgejo v7.0.3 can be released
Archived
Issues that must be fixed before Forgejo v7.0.4 can be released
Archived
Issues that must be fixed before Forgejo v8.0.0 can be released
Archived
Issues that must be fixed before Forgejo v9.0.0 can be released
Archived
Add this label to a PR to run all playwright tests manually.
Trigger additional tests on the PR when it is ready to be merged
manual testing has been documented
test should be added
help needed to add a test
no additional test is needed
test has been added
Pull requests that have been merged with no test and submitted as is to the dependency where they belong
Archived
Time tracking feature for issues and the JS stopwatch.
This PR was closed because the implementation is incomplete
Add this PR to the release notes
Requires input about accessibility features, likely involves user testing.
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
Instance-wide configuration, authentication and other admin-only needs.
How to deal with errors in the application and write helpful error messages.
How filter and search is being worked with.
The issue might be inspiring for future design work.
AGit, fork-based and new Git workflow, PR creation etc
Active research about Labels
Moderation Featuers for Admins are undergoing active User Research
Use this label to let the User Research team know their input is requested.
Research on how users should know what to do next.
Text rendering, markup languages etc
Active research about the New Repo dialog.
The repo sections, disabling them and the "Add more" button.
How to structure in-app settings in the future?
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?