mirror of
https://github.com/go-gitea/gitea.git
synced 2024-12-19 00:00:34 +01:00
8030614386
Fixes #24145 To solve the bug, I added a "computed" `TargetBehind` field to the `Release` model, which indicates the target branch of a release. This is particularly useful if the target branch was deleted in the meantime (or is empty). I also did a micro-optimization in `calReleaseNumCommitsBehind`. Instead of checking that a branch exists and then call `GetBranchCommit`, I immediately call `GetBranchCommit` and handle the `git.ErrNotExist` error. This optimization is covered by the added unit test. |
||
---|---|---|
.. | ||
access_token.yml | ||
access.yml | ||
action.yml | ||
attachment.yml | ||
collaboration.yml | ||
comment.yml | ||
commit_status_index.yml | ||
commit_status.yml | ||
deleted_branch.yml | ||
deploy_key.yml | ||
email_address.yml | ||
external_login_user.yml | ||
follow.yml | ||
gpg_key_import.yml | ||
gpg_key.yml | ||
hook_task.yml | ||
issue_assignees.yml | ||
issue_index.yml | ||
issue_label.yml | ||
issue_user.yml | ||
issue_watch.yml | ||
issue.yml | ||
label.yml | ||
lfs_meta_object.yml | ||
login_source.yml | ||
milestone.yml | ||
notice.yml | ||
notification.yml | ||
oauth2_application.yml | ||
oauth2_authorization_code.yml | ||
oauth2_grant.yml | ||
org_user.yml | ||
project_board.yml | ||
project_issue.yml | ||
project.yml | ||
protected_branch.yml | ||
public_key.yml | ||
pull_request.yml | ||
reaction.yml | ||
release.yml | ||
renamed_branch.yml | ||
repo_archiver.yml | ||
repo_indexer_status.yml | ||
repo_redirect.yml | ||
repo_topic.yml | ||
repo_transfer.yml | ||
repo_unit.yml | ||
repository.yml | ||
review.yml | ||
star.yml | ||
stopwatch.yml | ||
system_setting.yml | ||
team_repo.yml | ||
team_unit.yml | ||
team_user.yml | ||
team.yml | ||
topic.yml | ||
tracked_time.yml | ||
two_factor.yml | ||
user_open_id.yml | ||
user_redirect.yml | ||
user.yml | ||
watch.yml | ||
webauthn_credential.yml | ||
webhook.yml |