Loïc Dachary
c8f201f921
Merge pull request '[DOCS] RELEASE-NOTES: secrets are an implementation detail' ( #459 ) from earl-warren/forgejo:wip-1.19-release-notes-secrets into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/459
2023-03-02 09:46:02 +00:00
Loïc Dachary
5edabed4d4
Merge pull request '[DOCS] RELEASE-NOTES: OIDC groups' ( #464 ) from earl-warren/forgejo:wip-1.19-release-notes-oidc into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/464
2023-03-02 09:45:39 +00:00
Loïc Dachary
a5806290e2
Merge pull request '[DOCS] RELEASE-NOTES: Copy citation' ( #467 ) from earl-warren/forgejo:wip-1.19-release-notes-citation into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/467
2023-03-02 09:44:46 +00:00
Loïc Dachary
773be227fa
Merge pull request '[DOCS] RELEASE-NOTES: Support org/user level projects' ( #463 ) from earl-warren/forgejo:wip-1.19-release-notes-project into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/463
2023-03-02 09:44:00 +00:00
Loïc Dachary
557887e71e
Merge pull request '[DOCS] RELEASE-NOTES: Incoming emails' ( #458 ) from earl-warren/forgejo:wip-1.19-release-notes-incoming into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/458
2023-03-02 09:43:30 +00:00
Earl Warren
df7a2906d7
Merge pull request '[DOCS] RELEASE-NOTES: Prohibit fork if user reached maximum' ( #461 ) from earl-warren/forgejo:wip-1.19-release-notes-fork into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/461
2023-03-02 00:10:33 +00:00
Earl Warren
0f80b8c696
[DOCS] RELEASE-NOTES: Prohibit fork if user reached maximum
2023-03-02 01:09:44 +01:00
Earl Warren
8236dc3a57
[DOCS] RELEASE-NOTES: secrets are an implementation detail
2023-03-02 00:27:06 +01:00
Earl Warren
06c455b33b
[DOCS] RELEASE-NOTES: Incoming emails
2023-03-02 00:22:26 +01:00
Earl Warren
689301853b
Merge pull request '[DOCS] RELEASE-NOTES: v1.19 has a documentation' ( #453 ) from earl-warren/forgejo:wip-1.19-release-notes into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/453
2023-03-01 23:13:05 +00:00
Earl Warren
00ed020321
[DOCS] RELEASE-NOTES: do not split webhook section
2023-03-02 00:05:32 +01:00
Earl Warren
9a5b46da32
[DOCS] RELEASE-NOTES: v1.19 has a documentation
2023-03-02 00:05:32 +01:00
Earl Warren
55153b9e85
Merge pull request '[DOCS] RELEASE-NOTES: Scoped labels' ( #462 ) from earl-warren/forgejo:wip-1.19-release-notes-label into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/462
2023-03-01 22:53:28 +00:00
Earl Warren
de845c7bcf
[DOCS] RELEASE-NOTES: Support org/user level projects
2023-03-01 23:52:38 +01:00
Earl Warren
162560d26e
Merge pull request '[UI] Revert "Remove ONLY_SHOW_RELEVANT_REPOS setting"' ( #456 ) from earl-warren/forgejo:wip-relevant into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/456
2023-02-28 22:24:06 +00:00
Earl Warren
1681c51b7f
[UI] Revert "Remove ONLY_SHOW_RELEVANT_REPOS setting"
2023-02-28 19:36:20 +01:00
Earl Warren
d0f217735f
[DOCS] RELEASE-NOTES: Copy citation
2023-02-28 19:24:22 +01:00
Earl Warren
10c505fe89
[DOCS] RELEASE-NOTES: OIDC groups
2023-02-28 18:15:38 +01:00
Earl Warren
747479a07b
[DOCS] RELEASE-NOTES: Scoped labels
2023-02-28 17:08:21 +01:00
Earl Warren
28fab82302
Merge pull request '[DOCS] RELEASE-NOTES: add scoped access tokens' ( #454 ) from earl-warren/forgejo:wip-token-scope into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/454
2023-02-28 00:03:14 +00:00
Earl Warren
688f831853
[DOCS] RELEASE-NOTES: add scoped access tokens
2023-02-28 00:15:32 +01:00
Earl Warren
5739c7d5ad
Merge pull request '[DOCS] CONTRIBUTING/RELEASE: https://forgejo.org/docs/admin ' ( #452 ) from earl-warren/forgejo:wip-release-admin-doc into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/452
2023-02-27 20:14:23 +00:00
Earl Warren
83cc389239
[DOCS] CONTRIBUTING/RELEASE: https://forgejo.org/docs/admin
...
Because the version is not displayed on the landing page of Forgejo,
there cannot be a link to a versionned documentation. There must exist
a link that points to the latest version on the website for the
forgejo instance to display.
Better but more complicated approaches could be to:
* Embed the documentation in Forgejo
* Allow the admin to not display the help
* Allow the admin to display a versionned help or not
2023-02-27 19:20:26 +01:00
Earl Warren
de5cd8cb94
Merge pull request '[DOCS] RELEASE-NOTES: 1.19.0-0-rc0' ( #447 ) from dachary/forgejo:doc-release-notes-1.19.0 into forgejo-development
...
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/447
2023-02-27 10:27:14 +00:00
Loïc Dachary
e84e43887b
[DOCS] RELEASE-NOTES: 1.19.0-0-rc0
2023-02-27 11:21:45 +01:00
Loïc Dachary
db8392a8ac
[SECURITY] default to pbkdf2 with 320,000 iterations
...
(cherry picked from commit 3ea0b287d7
)
2023-02-25 15:50:53 +01:00
Earl Warren
1574643a6a
[API] Forgejo API /api/forgejo/v1
...
(cherry picked from commit 20b5669269
)
2023-02-25 15:50:53 +01:00
Percy Ma
79de60a5d8
[DOCS] LICENSE: add Forgejo Authors
...
(cherry picked from commit 7c98a4c54e
)
(cherry picked from commit 1ec4a8e6cf
)
2023-02-25 15:50:53 +01:00
Loïc Dachary
b07123ee7b
[DOCS] RELEASE-NOTES.md
2023-02-25 15:50:46 +01:00
Loïc Dachary
2ccd6e2bd6
[WORKFLOW] issues & pr templates
...
(cherry picked from commit 9dd224f00c
)
(cherry picked from commit 710af007bc
)
2023-02-25 15:50:46 +01:00
Loïc Dachary
67debe2247
[DOCS] README
...
(cherry picked from commit a47b474586
)
(cherry picked from commit 2fcc61c1d9
)
2023-02-25 15:50:46 +01:00
Loïc Dachary
08dcef0c8c
[DOCS] CONTRIBUTING
...
Refs: https://codeberg.org/forgejo/forgejo/issues/8
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/153
Refs: https://codeberg.org/forgejo/forgejo/issues/123
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/299
2023-02-25 15:50:37 +01:00
Loïc Dachary
ef43b1c691
delete Gitea specific files that need rewriting for Forgejo
...
Although it would be possible to modify these files, it would create
conflicts when rebasing. Instead, this commit removes them entirely
and another commit can start from scratch, borrowing content from the
original files.
The drawback of this approach is that some content updates from Gitea
that also need updating in Forgejo will have to be copy/pasted
instead of being merged.
(cherry picked from commit eb85782115
)
(cherry picked from commit 34401f2004
)
2023-02-25 15:48:41 +01:00
Loïc Dachary
3af8757583
[CI] set PASSWORD_HASH_ALGO = argon2 for integration tests
...
(cherry picked from commit 1d7ce2a39c
)
2023-02-25 13:55:40 +01:00
Loïc Dachary
8dff3cc2d1
[CI] implementation: forgejo container images
...
(cherry picked from commit dd1971d4e6
)
(cherry picked from commit 3981dbaf8c
)
2023-02-25 13:55:40 +01:00
Loïc Dachary
6b6007fbce
[CI] implementation: Woodpecker based CI
...
(cherry picked from commit c2a7aaeee8
)
2023-02-25 13:55:40 +01:00
Loïc Dachary
dc6e9d8799
[CI] implementation: publish forgejo- binaries instead of gitea-
...
(cherry picked from commit 6d910daafb
)
(cherry picked from commit d447861cc9
)
2023-02-25 13:55:40 +01:00
Yarden Shoham
8540fc45b1
Fix secrets overview page missing from docs sidebar ( #23143 )
...
There was a warning while building the docs: `Building sites … WARN
2023/02/25 08:56:37
"/workspace/gitea/docs/content/doc/secrets/overview.en-us.md:1:1":
duplicate menu entry with identifier "overview" in menu "sidebar"`.
### Before
![image](https://user-images.githubusercontent.com/20454870/221348741-55cef254-f2ac-4507-9a66-818b406c668f.png )
### After
![image](https://user-images.githubusercontent.com/20454870/221348757-42066303-e1b7-43fe-9c4f-e05182fbabdd.png )
Signed-off-by: Yarden Shoham <hrsi88@gmail.com>
2023-02-25 10:56:02 +01:00
Brecht Van Lommel
10cdcb9ea8
Add "Reviewed by you" filter for pull requests ( #22927 )
...
This includes pull requests that you approved, requested changes or
commented on. Currently such pull requests are not visible in any of the
filters on /pulls, while they may need further action like merging, or
prodding the author or reviewers.
Especially when working with a large team on a repository it's helpful
to get a full overview of pull requests that may need your attention,
without having to sift through the complete list.
2023-02-24 21:55:50 -05:00
Brecht Van Lommel
843f81113e
Projects: rename Board to Column in interface and improve consistency ( #22767 )
2023-02-24 18:10:50 -05:00
zeripath
d827215011
Fix DBConsistency checks on MSSQL ( #23132 )
...
Unfortunately xorm's `builder.Select(...).From(...)` does not escape the
table names. This is mostly not a problem but is a problem with the
`user` table.
This PR simply escapes the user table. No other uses of `From("user")`
where found in the codebase so I think this should be all that is
needed.
Fix #23064
Signed-off-by: Andrew Thornton <art27@cantab.net>
2023-02-24 16:45:55 -05:00
Brecht Van Lommel
f4920c9c7f
Add pagination for dashboard and user activity feeds ( #22937 )
...
Previously only the last few activities where available. This works for
all activity and for activity on a date chosen on the heatmap.
2023-02-24 16:15:10 -05:00
zeripath
740a5ecdd9
Update go.mod dependencies ( #23126 )
...
This PR does a bulk update of a lot of our go deps.
I have not included nektos/act and xorm for the following reasons:
* Xorm updates can sometimes be complex and I'd rather do that in a
separate PR
* I think people more update with the actions code should double check
that the latest nektos/act library works correctly.
---------
Signed-off-by: Andrew Thornton <art27@cantab.net>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2023-02-24 20:18:49 +00:00
Zettat123
347df0cbf0
Show empty repos in Admin Repository Management page ( #23114 )
...
The **Admin Repository Management** page and the **Explore Repository**
page both use the `RenderRepoSearch` function. In this function, the
`OnlyShowRelevant` search option is `true` when querying repositories
for admin page.
edf98a2dc3/routers/web/explore/repo.go (L99-L115)
Refer to
[#19361 ](https://github.com/go-gitea/gitea/pull/19361/files#diff-8058dfb85557010e0592d586675ec62ce406af7068e6311f39c160deac37f149R497 ),
the repositories with `is_empty=true` will be hidden if
`OnlyShowRelevant` is `true`.
Administrators should be able to see all repositories. So
`OnlyShowRelevant` shouldn't be set to `true` .
---------
Co-authored-by: Andrew Thornton <art27@cantab.net>
2023-02-24 19:11:31 +00:00
yp05327
9eb61b77ac
Redirect to the commit page after applying patch ( #23056 )
...
Fixes https://github.com/go-gitea/gitea/issues/22621
2023-02-24 16:56:41 +00:00
WÁNG Xuěruì
e77528baed
Bump go.etcd.io/bbolt and blevesearch deps ( #23062 )
...
This notably brings support for GOARCH=loong64, among other fixes.
---------
Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
Co-authored-by: zeripath <art27@cantab.net>
2023-02-24 15:45:28 +00:00
HesterG
d20b29d7ce
Fix height for sticky head on large screen on PR page ( #23111 )
...
Right now on the PR 'File Change' Tab, the file title header sticky to
the top on large screens has wrong height, resulting in wrong ui
behavior when scrolling down. This PR is to fix this.
Before:
<img width="964" alt="截屏2023-02-24 17 12 29"
src="https://user-images.githubusercontent.com/17645053/221140409-025c4a84-6bbe-4b5b-a13f-bd2b79063522.png ">
After:
<img width="1430" alt="截屏2023-02-24 21 10 12"
src="https://user-images.githubusercontent.com/17645053/221186750-0344d652-4610-4a90-a4c0-7f6269f950d6.png ">
2023-02-24 14:29:49 +00:00
Lunny Xiao
a8c4f8cebc
Fix db.Find bug ( #23115 )
...
Caused by #20821
Fix #23110
2023-02-24 21:17:09 +08:00
Lunny Xiao
91fa0eb9d7
Avoid warning for system setting when start up ( #23054 )
...
Partially fix #23050
After #22294 merged, it always has a warning log like `cannot get
context cache` when starting up. This should not affect any real life
but it's annoying. This PR will fix the problem. That means when
starting up, getting the system settings will not try from the cache but
will read from the database directly.
---------
Co-authored-by: Lauris BH <lauris@nix.lv>
2023-02-24 18:23:13 +08:00
Jason Song
edf98a2dc3
Require approval to run actions for fork pull request ( #22803 )
...
Currently, Gitea will run actions automatically which are triggered by
fork pull request. It's a security risk, people can create a PR and
modify the workflow yamls to execute a malicious script.
So we should require approval for first-time contributors, which is the
default strategy of a public repo on GitHub, see [Approving workflow
runs from public
forks](https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks ).
Current strategy:
- don't need approval if it's not a fork PR;
- always need approval if the user is restricted;
- don't need approval if the user can write;
- don't need approval if the user has been approved before;
- otherwise, need approval.
https://user-images.githubusercontent.com/9418365/217207121-badf50a8-826c-4425-bef1-d82d1979bc81.mov
GitHub has an option for that, you can see that at
`/<owner>/<repo>/settings/actions`, and we can support that later.
<img width="835" alt="image"
src="https://user-images.githubusercontent.com/9418365/217199990-2967e68b-e693-4e59-8186-ab33a1314a16.png ">
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2023-02-24 15:58:49 +08:00