| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Resolves https://github.com/go-gitea/gitea/issues/34435
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fix #34400
---------
Co-authored-by: silverwind <me@silverwind.io>
|
|
|
| |
Try to fix #32046
|
|
|
|
|
| |
update the databse (#34422)
Fix #34318
|
|
|
|
| |
These functions have been marked as `panicIfDevOrTesting` since 1.23
(#32422)
|
|
|
| |
Fix #34418, fix #34353
|
| |
|
|
|
| |
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Merge the CSS for the two expanders (text-expander-element and
tribute.js) into one file
- Fix overflow issues
- Remove min-width
- Various other tweaks like borders, colors, padding, gaps.
text-expander:
<img width="645" alt="Screenshot 2025-05-09 at 02 21 24"
src="https://github.com/user-attachments/assets/33276dc4-38e8-45e1-8216-2a4baa9bc039"
/>
tribute:
<img width="624" alt="Screenshot 2025-05-09 at 02 21 37"
src="https://github.com/user-attachments/assets/91fbcd1a-9bfc-40fd-93f0-a05b4bd4c98d"
/>
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
| |
Tested, it works as before.
Changelog:
https://github.com/github/relative-time-element/releases/tag/v4.4.8
Signed-off-by: Yarden Shoham <git@yardenshoham.com>
|
|
|
|
|
|
| |
Fix #34398, fix #33308
Remove all `repo.ComposeCommentMetas` from templates,
only use `repo` to render commit message.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "autofocus" was abused or misbehaved:
1. When users visit a page but they are not going to change a field,
then the field shouldn't get "autofocus"
* the "auth" / "user" page: in most cases, users do not want to change
the names
* see also the GitHub's "settings" page behavior.
2. There shouldn't be duplicate "autofocus" inputs in most cases, only
the first one focuses
3. When a panel is shown, the "autofocus" should get focus
* "add ssh key" panel
This PR fixes all these problems and by the way remove duplicate
"isElemHidden" function.
|
|
|
|
|
|
|
|
|
|
| |
Issue: After switching the default branch, other branches are still
compared against the old default branch due to outdated divergence
cache.
Change: Clear the divergence cache in SetRepoDefaultBranch to ensure
correct comparisons against the new default branch.
Fixes #34369
|
|
|
|
|
|
|
|
| |
Add a button editing action secret
Closes #34190
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
| |
Files that should be stored in LFS and are uploaded/edited from the API
or web UI aren't stored in LFS. This may be a regression from #34154.
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
#34298" (#34321)
There is a known issue where scrolling to the bottom of the page is
affected by unknown elements in the footer area:
https://github.com/go-gitea/gitea/blob/24145f811069295b9727f25469f1dd3a7c2c5dd7/templates/base/footer.tmpl#L11-L18

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This PR adds the label _state_ to the metric _gitea_users_. With the
change, _gitea_users_ would be reported like this:
```
...
# HELP gitea_users Number of Users
# TYPE gitea_users gauge
gitea_users{state="active"} 20
gitea_users{state="inactive"} 10
...
```
The metrics above would be from a Gitea instance with 30 user accounts.
20 of the accounts are active and 10 of the accounts are not active.
Resolve #34325
|
|
|
| |
Result of `make update-js update-py svg`. Quick test of the UI worked.
|
|
|
|
|
| |
There will be a possible bug when migrating from Github
https://github.com/google/go-github/issues/3229
This PR upgrades go-github from v61 to v71 to resolve that problem.
|
|
|
|
|
|
|
| |
Tested, it works as before.
Changelog:
https://github.com/github/relative-time-element/releases/tag/4.4.7
Signed-off-by: Yarden Shoham <git@yardenshoham.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Grey out expired artifact on Artifacts list.


---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
| |
Regression from #34356, files like SVGs should be editable too
(https://github.com/go-gitea/gitea/pull/34356#discussion_r2072766240).
|
|
|
|
|
|
|
| |
This PR adds me as a _maintainer_ as suggested by @techknowlogick.
A couple of my recent PRs:
* https://github.com/go-gitea/gitea/pull/34324
* https://github.com/go-gitea/gitea/pull/34323
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Before

After

|
| |
|
|
|
|
| |
The `ci.HeadGitRepo` was opened and closed in the function
`ParseCompareInfo` but reused in the function `PrepareCompareDiff`.
|
|
|
|
|
| |
It's possible to edit "raw" lfs files in the web UI when accessing the path manually.

|
|
|
|
|
|
|
|
| |
Tested, it works as before.
Changelog:
https://github.com/github/relative-time-element/releases/tag/v4.4.6
Signed-off-by: Yarden Shoham <git@yardenshoham.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
before:

after:

The difference is minimal, only a few pixels above and beneath, but it
stands out when switching fast between the tabs on the explore route.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#34323)
In the Gitea GUI, the user can see the time that _AccessTokens_ and
_PublicKeys_ were last used. This information is not returned by the
_/users/{username}/tokens_ and _/user/keys_ endpoints in the API. This
PR adds the missing data.
The time of last usage for for _tokens_ & _keys_ seem to be stored in
the _Updated_ field of the structs internally. For consistency, I have
used the name _updated_at_ for the new field returned by the _API_.
However, for the _API_ user, I don't think that name reflects the data
returned, as I believe it is the time of last usage. I propose that we
use the name _last_used_at_ instead. Let's hear reviewers opinion on
that.
* PublicKey
1. _last_used_at_: string($date-time)
* AccessToken
1. _created_at_: string($date-time) (for parity with public keys)
2. _last_used_at_: string($date-time)
Fix #34313
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#34324)
If archive downloads are are disabled using
_DISABLE_DOWNLOAD_SOURCE_ARCHIVES_, archive links are still returned by
the API.
This PR changes the data returned, so the fields _zipball_url_ and
_tarball_url_ are omitted if archive downloads have been disabled.
Resolve #32159
|
|
|
| |
Also fix #34300
|
| |
|
|
|
| |
Continue with #34206.
|
|
|
|
| |
go cmd will download and cache a copy of the Go toolchain, go1.24 is not
a valid version since https://github.com/golang/go/issues/57631.
|
|
|
|
|
|
| |
Fix
https://github.com/go-gitea/gitea/actions/runs/14722306878/job/41318217870
A fork has been created under https://gitea.com/gitea/go-xsd-duration
|
|
|
| |
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
| |
Fix #34224
The previous implementation in #33744 will get the pushed commits
changed files. But it's not always right when push a merged commit. This
PR reverted the logic in #33744 and will always get the PR's changed
files and get code owners.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix #880
Design:
1. A global setting `security.TWO_FACTOR_AUTH`.
* To support org-level config, we need to introduce a better "owner
setting" system first (in the future)
2. A user without 2FA can login and may explore, but can NOT read or
write to any repositories via API/web.
3. Keep things as simple as possible.
* This option only aggressively suggest users to enable their 2FA at the
moment, it does NOT guarantee that users must have 2FA before all other
operations, it should be good enough for real world use cases.
* Some details and tests could be improved in the future since this
change only adds a check and seems won't affect too much.
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
* fixes a fixture status to upload confirmed
* add another fixture as noise to break tests as soon they are exposed
to api
* v4 delete test added check that artifact is no longer visible in
internal api with status pending delete
* removal of http 404 on empty list: actions/upload-artifact@v4 now
backoff on http 404 of ListArtifacts endpoint
* fixes artifacts with pending delete etc. are able to be found and
downloaded if the storage is not freed
|
|
|
|
|
|
|
|
| |
Continue with #34206.
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
|
|
|
| |
Fix #34231
|
| |
|
|
|
|
|
|
|
| |
Fix #34275
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|