Backport #34061 by eeyrjmr
The doctor storage check reconstructs the lfs oid by producing a string
where the path separator is stripped
ab/dc/efg -> abdcefg. Windows however uses a backslash and thus the
ReplaceAll call doesn't produce the correct oid resulting in all lfs
objects being classed as orphaned.
This PR allows this to be more OS agnostic.
Closes#34039
Co-authored-by: JonRB <4564448+eeyrjmr@users.noreply.github.com>
Fix#33490
Backport #33744
It will only read the changed file on the pushed commits but not all the
files of this PR.
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Backport #33597 by @ericLemanissier
follows-up be4e961240883778c44d9651eaaf9ab8723bbbb0
This is the same modification as
be4e961240
but for force-pushes.
It is needed, because `git fetch` reveals force pushes for github
mirrors:
```
$ git fetch --tags origin
remote: Enumerating objects: 22, done.
remote: Counting objects: 100% (22/22), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 9 (delta 5), reused 8 (delta 5), pack-reused 0 (from 0)
Unpacking objects: 100% (9/9), 1.70 KiB | 12.00 KiB/s, done.
From https://github.com/conan-io/conan-center-index
729f0f1b8f..48184eddeb refs/pull/26595/head -> refs/pull/26595/head
+ 0c31ab60a3...1283cca9e7 refs/pull/26595/merge -> refs/pull/26595/merge (forced update)
```
Fix https://github.com/go-gitea/gitea/issues/33200
PS: I did not test the modification, but it is the exact same change as
the last hunk in
https://github.com/go-gitea/gitea/pull/33224/files#diff-bb5cdb90db0f0e7f6716c0e6d0b9cbb67f08d82052b03ab3a7b5e23a1d76aed7
, just moved to the previous case of the switch
Co-authored-by: ericLemanissier <ericLemanissier@users.noreply.github.com>
Backport #33262 by ExplodingDragon
Only show the latest version of the package in the arch repo.
closes#33534
Co-authored-by: Exploding Dragon <explodingfkl@gmail.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Backport #33569 by @wxiaoguang
* Make artifact list output has stable order
* Fix#33506
* Fix#33521
* Fix#33288
* Fix#33196
* Fix#33561
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Backport #33543
In the old `pickTask`, when getting secrets or variables failed, the
task could get stuck in the `running` status (task status is `running`
but the runner did not fetch the task). To fix this issue, these steps
should be in one transaction.
---------
Co-authored-by: Zettat123 <zettat123@gmail.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
This PR created a mock webhook server in the tests and added integration
tests for generic webhooks.
It also fixes bugs in package webhooks and pull request comment
webhooks.
This also corrected an error on the package webhook. The previous
implementation uses a `User` struct as an organization, now it has been
corrected but it will not be consistent with the previous
implementation, some fields which not belong to the organization have
been removed.
Backport #33396
Backport part of #33337
Try to backport #33315, the only trivial conflict is in the helper
functions map in the helper.go
Fix#33333
Co-authored-by: Sysoev, Vladimir <i@vsysoev.ru>
Backport #33147 by changchaishi
Fixes#33145
An integration test could be added.
---------
Co-authored-by: Chai-Shi <changchaishi@gmail.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Backport #32999 by @a1012112796
user with read permission should also can create agit flow pull request.
looks this logic was broken in
https://github.com/go-gitea/gitea/pull/31033 this pull request try fix
it and add test code.
Signed-off-by: a1012112796 <1012112796@qq.com>
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Backport #32946 by wxiaoguang
Fix#23703
When Gitea starts, it reads GITEA_RUNNER_REGISTRATION_TOKEN
or GITEA_RUNNER_REGISTRATION_TOKEN_FILE to add registration token.
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Backport #32881 by ExplodingDragon
Incorrect content was introduced while generating the index, which has
now been removed, and the missing fields have been added.
Co-authored-by: Exploding Dragon <explodingfkl@gmail.com>
