DmitryFrolovTri
e3b462819b
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-02-06 06:21:12 +00:00
KN4CK3R and Lunny Xiao
d987ac6bf1
Add Chef package registry ( #22554 )
...
This PR implements a [Chef registry](https://chef.io/ ) to manage
cookbooks. This package type was a bit complicated because Chef uses RSA
signed requests as authentication with the registry.


Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-02-06 09:49:21 +08:00
KN4CK3R and Lunny Xiao
df789d962b
Add Cargo package registry ( #21888 )
...
This PR implements a [Cargo registry](https://doc.rust-lang.org/cargo/ )
to manage Rust packages. This package type was a little bit more
complicated because Cargo needs an additional Git repository to store
its package index.
Screenshots:



---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-02-05 18:12:31 +08:00
8574a6433f
Show all projects, not just repo projects and open/closed projects ( #22640 )
...
This PR fixes two problems. One is when filter repository issues, only
repository level projects are listed. Another is if you list open
issues, only open projects will be displayed in filter options and if
you list closed issues, only closed projects will be displayed in filter
options.
In this PR, both repository level and org/user level projects will be
displayed in filter, and both open and closed projects will be listed as
filter items.
---------
Co-authored-by: John Olheiser <john.olheiser@gmail.com >
Co-authored-by: zeripath <art27@cantab.net >
Co-authored-by: delvh <dev.lh@web.de >
2023-02-04 22:35:08 +08:00
DmitryFrolovTri
82dcd0c3cf
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-02-03 14:17:44 +00:00
zeripath and delvh
2914c5299b
Improve error report when user passes a private key ( #22726 )
...
The error reported when a user passes a private ssh key as their ssh
public key is not very nice.
This PR improves this slightly.
Ref #22693
Signed-off-by: Andrew Thornton <art27@cantab.net >
Co-authored-by: delvh <dev.lh@web.de >
2023-02-02 18:25:54 +00:00
KN4CK3R
6ba9ff7b48
Add Conda package registry ( #22262 )
...
This PR adds a [Conda](https://conda.io/ ) package registry.
2023-02-01 12:30:39 -06:00
DmitryFrolovTri
9da8b9db8e
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-02-01 18:16:48 +00:00
KN4CK3R and Lunny Xiao
5882e179a9
Add user secrets ( #22191 )
...
Fixes #22183
Replaces #22187
This PR adds secrets for users. I refactored the files for organizations
and repos to use the same logic and templates. I splitted the secrets
from deploy keys again and reverted the fix from #22187 .
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-02-01 20:53:04 +08:00
yp05327 and Jason Song
72a83dcc82
Explain that the no-access team unit does not affect public repositories ( #22661 )
...
Fixes https://github.com/go-gitea/gitea/issues/22600
Add explanations to team unit access control.
---------
Co-authored-by: Jason Song <i@wolfogre.com >
2023-02-01 16:14:40 +08:00
Felipe Leopoldo Sologuren Gutiérrez
7fd5d38860
Improve checkbox accessibility a bit by adding the title attribute ( #22593 )
...
EDIT: The main change of this PR was resolved by #22599 . This
complements that PR for some cases without label and complicated layout
to be added.
NOTE: Contributed by @Forgejo.
2023-02-01 01:43:06 +00:00
Brecht Van Lommel
faa96553d1
Add repository setting to enable/disable releases unit ( #22671 )
...
To go along with similar settings for issues, pulls, projects, packages.
2023-02-01 01:31:19 +00:00
4011821c94
Implement actions ( #21937 )
...
Close #13539 .
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png ">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png ">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png ">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source ).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png ">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner ), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md )
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png ">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png ">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png ">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png ">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart )
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png ">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png ">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions )
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/ )
---------
Co-authored-by: a1012112796 <1012112796@qq.com >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: delvh <dev.lh@web.de >
Co-authored-by: ChristopherHX <christopher.homberger@web.de >
Co-authored-by: John Olheiser <john.olheiser@gmail.com >
2023-01-31 09:45:19 +08:00
DmitryFrolovTri
7b4e90b9d0
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-29 09:33:49 +00:00
techknowlogick and Brecht Van Lommel
e88b529b31
Issues: add Project filter to issues list and search ( #22544 )
...
Currently only a single project like milestone, not multiple like
labels.
Implements #14298
Code by @brechtvl
---------
Co-authored-by: Brecht Van Lommel <brecht@blender.org >
2023-01-29 11:45:29 +08:00
Felipe Leopoldo Sologuren Gutiérrez and Lunny Xiao
2b1e47e2a2
Improve accessibility of navigation bar and footer ( #22635 )
...
Added ARIA navigation landmark to navigation bar and aria label for both
nav bar and footer.
Contributed by @forgejo.
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-01-29 09:29:10 +08:00
Otto Richter (fnetX) and Lunny Xiao
95d9fbdcf3
Fix error on account activation with wrong passwd ( #22609 )
...
On activating local accounts, the error message didn't differentiate
between using a wrong or expired token, or a wrong password. The result
could already be obtained from the behaviour (different screens were
presented), but the error message was misleading and lead to confusion
for new users on Codeberg with Forgejo.
Now, entering a wrong password for a valid token prints a different
error message.
The problem was introduced in 0f14f69e60 .
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-01-28 15:59:46 +08:00
DmitryFrolovTri
7aeb909d57
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-19 04:44:05 +00:00
Lunny Xiao
f59ce77772
Display unreferenced packages total size in package admin panel ( #22498 )
2023-01-18 09:52:04 -06:00
DmitryFrolovTri
bcea146ed2
Fix merge conflig in migrations.go Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-18 04:56:35 +00:00
Chongyi Zheng
de484e86bc
Support scoped access tokens ( #20908 )
...
This PR adds the support for scopes of access tokens, mimicking the
design of GitHub OAuth scopes.
The changes of the core logic are in `models/auth` that `AccessToken`
struct will have a `Scope` field. The normalized (no duplication of
scope), comma-separated scope string will be stored in `access_token`
table in the database.
In `services/auth`, the scope will be stored in context, which will be
used by `reqToken` middleware in API calls. Only OAuth2 tokens will have
granular token scopes, while others like BasicAuth will default to scope
`all`.
A large amount of work happens in `routers/api/v1/api.go` and the
corresponding `tests/integration` tests, that is adding necessary scopes
to each of the API calls as they fit.
- [x] Add `Scope` field to `AccessToken`
- [x] Add access control to all API endpoints
- [x] Update frontend & backend for when creating tokens
- [x] Add a database migration for `scope` column (enable 'all' access
to past tokens)
I'm aiming to complete it before Gitea 1.19 release.
Fixes #4300
2023-01-17 15:46:03 -06:00
DmitryFrolovTri
3429b994d8
Fix merge conflict in migrations.go, v238.go, create v999.go and Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-17 09:58:29 +00:00
KN4CK3R
8117e41dfa
Add reply hint to mail text ( #22459 )
...
Addition to #22056
This PR adds a hint to mail text if replies are supported.
I can't tell if the text structure is supported in every language. Maybe
we need to put the whole line in the translation file and use
parameters.
2023-01-16 14:58:01 -06:00
zeripath
2cc3a6381c
Add cron method to gc LFS MetaObjects ( #22385 )
...
This PR adds a task to the cron service to allow garbage collection of
LFS meta objects. As repositories may have a large number of
LFSMetaObjects, an updated column is added to this table and it is used
to perform a generational GC to attempt to reduce the amount of work.
(There may need to be a bit more work here but this is probably enough
for the moment.)
Fix #7045
Signed-off-by: Andrew Thornton <art27@cantab.net >
2023-01-16 13:50:53 -06:00
Lunny Xiao and zeripath
2782c14396
Supports wildcard protected branch ( #20825 )
...
This PR introduce glob match for protected branch name. The separator is
`/` and you can use `*` matching non-separator chars and use `**` across
separator.
It also supports input an exist or non-exist branch name as matching
condition and branch name condition has high priority than glob rule.
Should fix #2529 and #15705
screenshots
<img width="1160" alt="image"
src="https://user-images.githubusercontent.com/81045/205651179-ebb5492a-4ade-4bb4-a13c-965e8c927063.png ">
Co-authored-by: zeripath <art27@cantab.net >
2023-01-16 16:00:22 +08:00
DmitryFrolovTri
ac99056ad2
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-13 12:11:59 +00:00
crystal
4fc1517da0
clarify "open issues" text for labels ( #22431 )
...
see also https://codeberg.org/Codeberg/Community/issues/877
2023-01-13 12:40:39 +01:00
DmitryFrolovTri
80fa68ba12
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-10 12:33:28 +00:00
Yarden Shoham
3b804ff76c
Fix "remember this device" case ( #22388 )
...
In the title case, it should be "Remember This Device"
Signed-off-by: Yarden Shoham <hrsi88@gmail.com >
2023-01-10 17:43:54 +08:00
DmitryFrolovTri
6060ae1bbd
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2023-01-09 04:50:53 +00:00
delvh
b878155b87
Replace can not with cannot ( #22372 )
...
Fixes #22371 .
2023-01-08 18:25:28 +00:00
KN4CK3R
b1a4eb40a1
[skip ci] Updated licenses and gitignores
2023-01-01 00:19:35 +00:00
DmitryFrolovTri
2763393f39
Merge remote-tracking branch 'upstream/main' into limit-repo-size
...
Conflicts:
models/migrations/migrations.go
models/migrations/v1_19/v237.go
new file: models/migrations/v1_19/v238.go
2022-12-25 09:40:26 +00:00
Lunny Xiao
3bd49f7801
[skip ci] Updated licenses and gitignores
2022-12-25 00:19:36 +00:00
Reo
48d71b7d6b
Add Feed for Releases and Tags ( #21696 )
...
Fixes #19091
Add Feed for Releases and Tags, can be accessed through
`reponame/releases.rss`, `reponame/releases.atom`, `reponame/tags.rss`,
and `reponame/tags.atom`
Signed-off-by: Reo <reo_999@proton.me >
2022-12-21 15:06:26 -06:00
DmitryFrolovTri
e26bcfca60
Merge remote-tracking branch 'upstream/main' into limit-repo-size
...
Resolved Conflicts:
models/migrations/migrations.go
models/migrations/v1_19/v236.go
new file: v237.go
2022-12-21 10:45:16 +00:00
659055138b
Secrets storage with SecretKey encrypted ( #22142 )
...
Fork of #14483 , but [gave up
MasterKey](https://github.com/go-gitea/gitea/pull/14483#issuecomment-1350728557 ),
and fixed some problems.
Close #12065 .
Needed by #13539 .
Featrues:
- Secrets for repo and org, not user yet.
- Use SecretKey to encrypte/encrypt secrets.
- Trim spaces of secret value.
- Add a new locale ini block, to make it easy to support secrets for
user.
Snapshots:
Repo level secrets:

Rrg level secrets

Co-authored-by: Lauris BH <lauris@nix.lv >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com >
Co-authored-by: delvh <dev.lh@web.de >
Co-authored-by: KN4CK3R <admin@oldschoolhack.me >
2022-12-20 17:07:13 +08:00
DmitryFrolovTri
cdc5a2caf7
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2022-12-19 09:53:10 +00:00
zeripath
998fe26051
[skip ci] Updated licenses and gitignores
2022-12-18 00:19:33 +00:00
DmitryFrolovTri
d1368ecfb6
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2022-12-14 05:27:36 +00:00
KN4CK3R
601d126627
[skip ci] Updated licenses and gitignores
2022-12-11 00:19:34 +00:00
DmitryFrolovTri
4687f0c779
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2022-12-08 18:05:12 +00:00
Jason Song
8fb1e53ca2
Rename actions to operations on UI ( #22067 )
...
Use "operations" to indicate "some something can be done", to prevent
users from confusing it with CICD.
Releated to: #13539 .
Snapshots:
<img width="389" alt="image"
src="https://user-images.githubusercontent.com/9418365/206409797-a99bac25-2d38-4066-b9ab-27a4f6fe67e7.png ">
<img width="398" alt="image"
src="https://user-images.githubusercontent.com/9418365/206410099-bbd258a9-54d9-4664-8d95-31d29cb35209.png ">
<img width="442" alt="image"
src="https://user-images.githubusercontent.com/9418365/206410218-009a3103-a9b9-4d0c-86b6-540dda5bce89.png ">
I'm not a native English speaker, but I think "operations" may be good
enough, and Gitea already uses this word:
<img width="1440" alt="image"
src="https://user-images.githubusercontent.com/9418365/206410671-4a718b14-0603-40cb-bdcb-f6f84d1f5e24.png ">
2022-12-08 21:14:09 +08:00
DmitryFrolovTri
4c0921eb3b
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2022-12-04 06:54:29 +00:00
zeripath
d084ce306a
[skip ci] Updated licenses and gitignores
2022-12-04 00:19:34 +00:00
DmitryFrolovTri
b391383936
Merge remote-tracking branch 'upstream/main' into limit-repo-size
2022-11-30 13:32:28 +00:00
花墨 and wxiaoguang
7020c4afb7
Fix leaving organization bug on user settings -> orgs ( #21983 )
...
Fix #21772
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com >
2022-11-30 17:00:00 +08:00
luzpaz
fdfd77f478
Fix typos ( #21979 )
...
Found via codespell
2022-11-29 18:41:29 -06:00
KN4CK3R
32590db4ca
[skip ci] Updated licenses and gitignores
2022-11-27 00:19:33 +00:00
DmitryFrolovTri
ee31efc6b1
fix migrations.go conflict
2022-11-24 17:13:26 +00:00