(cherry picked from commit a47b474586)
(cherry picked from commit 2fcc61c1d929380884dd9aeb143c202a2be0eef9)
(cherry picked from commit 67debe2247c83753173efba53c60845f522857b5)
(cherry picked from commit b90ffbb309bc76968588a024d2ced081989295ea)
(cherry picked from commit 07a744814855a8bcb8d196c6c31f9bde7cfcf249)
(cherry picked from commit a7fe270c08c25e6db42c32019b4a1a0720a57ec1)
(cherry picked from commit 2f15389a9cafa00001c84396a1a88a14c3250e5c)
(cherry picked from commit 16ba587f5dbbfa36398ca55e5210e5233211e224)
(cherry picked from commit 683a23b2ca29f3638a2bd703dad567ae2896f261)
(cherry picked from commit 3e5de3f656fa769317bf1cd1e508682f89e90000)
(cherry picked from commit 5789005c4355f9d6b76a2288376b3b45a7939ba0)
(cherry picked from commit 75c0f11079bc1e376b55186c4994bea71a54cd15)
(cherry picked from commit e78a272e111066950ad5a365e504e1aacb4de5b7)
(cherry picked from commit 464a534a3a712111b5578523bb657cd36cb10f64)
(cherry picked from commit 7c0b73ca6fc28696fd580d7f858f8d814436e9a6)
(cherry picked from commit e66b8edbc6)
(cherry picked from commit a91864340d75d16e6afce18e7e5b974cfae8719f)
(cherry picked from commit 504905bc882ad075f821fb4fcd86560191bdada9)
(cherry picked from commit 650137433f44d65570947c8dbad6fb51b18f8a68)
(cherry picked from commit 3e00bdaf2a2d47d168108cd130829d6d864fa4b4)
(cherry picked from commit 43efcc1a29449c802b18a09387af67c24e71b189)
(cherry picked from commit 4984ba13c57fdade1a5744713c98a60e650a5b9a)
(cherry picked from commit 02b7928710ad9446b93598801dff0afae828136a)
(cherry picked from commit 0db0feaee25187bcd4c28c9e66d3d0eabaad7a8d)
(cherry picked from commit 94d141bc7f488ab0e6512218cac409b63cf83700)
(cherry picked from commit 392fb1589178338b8285df7b348754e79611590e)
(cherry picked from commit c5699a7bb71962321b131c9ac4413f8710de0d56)
(cherry picked from commit b975597a781c745463d9db80a220733d99a12e28)
(cherry picked from commit 5395e74d72285490f25067c8ac72899a3e23f3e7)
(cherry picked from commit bc8060dee4355667680dab8935a7abd504ceefbd)
(cherry picked from commit 3b64f1477a50319c3dbf638c89ef04dbd2fc12af)
(cherry picked from commit d40378e1c767194b2207d359378a976f1f0c9090)
(cherry picked from commit a713f7e3f9f6f8231d2cba82833d8eabec8b0dd4)
(cherry picked from commit 87f65ccf78eb19e573971c8c16a76f60d610a5d5)
(cherry picked from commit 049ea571a90853cb9bc1ce054313055884f76513)
(cherry picked from commit 433d1d7baae7e72b32b8d2febdf0bf01d925bbf3)
(cherry picked from commit 21bed2af1de216304dac33c33865bb70e31e416d)
(cherry picked from commit fe700ca401)
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 34401f2004445f225a479b8258180f498ac87847)
(cherry picked from commit ef43b1c6910a01a5f9dbd054e23372f6f17f4d9e)
(cherry picked from commit d17fe25e2f915e778eb968c20939dc253f47bcd5)
(cherry picked from commit 3f65dea3e7a5d0983d96d7011385125bd0063ff1)
(cherry picked from commit 3cacb64a1bae713467d3d9b7ebfe626930f2bd35)
(cherry picked from commit b531b014b751233b46e3220c25108fe95531621b)
(cherry picked from commit adf6e7a840c7f7201eddec3ab2b305200b19fc43)
(cherry picked from commit 68c19d977d6aa8e8eb5714f5915b6557379887c0)
(cherry picked from commit 31aa8647ecaf91704652e149fb5d0e891645412d)
(cherry picked from commit be70dd7208c2b40842cb83affa77f6d15ac4d840)
(cherry picked from commit 7f44bb60b16843b0e127a7e5fc89736a1d35d145)
(cherry picked from commit 5098f1224b10ac7b35c1d4c9ece8fbd066a616e8)
(cherry picked from commit dc7a8591442772f9801bfff7a77f1c8806bedb5c)
(cherry picked from commit f1e78dd0067f8d0e9a6ea4dc292ebebdb8b8bcda)
(cherry picked from commit c41ba7a148)
(cherry picked from commit f1da66a918a68237894e220d206a5e0251ec85d0)
(cherry picked from commit 99194a3664dc94296f7e1397be45b6fde9e3e718)
(cherry picked from commit 52f356f6a9dbbbd4e2c68fde99f7c35a3e6f2bd0)
(cherry picked from commit c93ffa72ae35bbdc6cc470823648a1aed0185b5d)
(cherry picked from commit 477c7454d39e813e2bc5107bf84105060acfe743)
(cherry picked from commit 413df23a407547b1a0d480185be9efc388b464eb)
[DOCS] delete Gitea specific files that need rewriting for Forgejo (squash)
(cherry picked from commit df78cedd053e624bcc30b048eac9d6ab10ff5749)
(cherry picked from commit 3b9178b3e5ee1aedff79a6ff5b62fb700f480682)
(cherry picked from commit 9044dcb0e7bb410bbc8a83c8d3610fa6c8355e25)
(cherry picked from commit e138685bacc14138aad46bea2756dc4f6d6b46c0)
(cherry picked from commit 2f1f3fd6b8a7b054bf854ea94ef91c8f87bce996)
(cherry picked from commit 0b47d02df6c93129d825aa1b9d3f481b6cf7f505)
(cherry picked from commit 7625ca6c42b6a333e3a2e25dd3df2744a4180e32)
(cherry picked from commit e0d720a728cf24eaeb1416ac1c5b8de6655ccd44)
(cherry picked from commit 19aa974d120fe5ade8436e5ea0fab6a83f1b9db1)
(cherry picked from commit bb637d398cb02e2d0059a1e7660b88bfe87e3315)
(cherry picked from commit 5357fc952d29b5f38ad95b3c94fca22e16217578)
(cherry picked from commit bee03950445384c4d985617793175bb7b27810a1)
(cherry picked from commit 5e574bfc8f761ad631aaadda6fa4c44ac826153b)
(cherry picked from commit 9593225c5bfbf0ac5cddd62359c812b755995397)
(cherry picked from commit f6e5faee613947755c85807ab6b06fe8008aed9b)
(cherry picked from commit 02f2a9a47a9084a6218d67f773d474febbb5fa54)
(cherry picked from commit 68695685c1)
Move `public/*` to `public/assets/*`
Some old PRs (like #15219) introduced inconsistent directory system.
For example: why the local directory "public" is accessed by
`http://site/assets`? How to serve the ".well-known" files properly in
the public directory?
For convention rules, the "public" directory is widely used for the
website's root directory. It shouldn't be an exception for Gitea.
So, this PR makes the things consistent:
* `http://site/assets/foo` means `{CustomPath}/public/assets/foo`.
* `{CustomPath}/public/.well-known` and `{CustomPath}/public/robots.txt`
can be used in the future.
This PR is also a prerequisite for a clear solution for:
* #21942
* #25892
* discourse.gitea.io: [.well-known path serving custom files behind
proxy?](https://discourse.gitea.io/t/well-known-path-serving-custom-files-behind-proxy/5445/1)
This PR is breaking for users who have custom "public" files (CSS/JS).
After getting approvals, I will update the documents.
----
## ⚠️ BREAKING ⚠️
If you have files in your "custom/public/" folder, please move them to
"custom/public/assets/".
---------
Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Giteabot <teabot@gitea.io>
@techknowlogick
Only added a placeholder, the index is possibly wrong. But I think you
need to do/finalize that as the opencollective holder :)
You can take the logo of the opencollective account. LMK if I can help
more!
Co-authored-by: Lauris BH <lauris@nix.lv>
Co-authored-by: techknowlogick <matti@mdranta.net>
Use Golang 1.18 (as minimal requirement) for Gitea 1.17 release, make sure the Golang version is still actively supported during Gitea 1.17 lifecycle.
Co-authored-by: zeripath <art27@cantab.net>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: 6543 <6543@obermui.de>
* use go1.18 to build gitea& update min go version to 1.17
* bump in a few more places
* add a few simple tests for isipprivate
* update go.mod
* update URL to https://go.dev/dl/
* golangci-lint
* attempt golangci-lint workaround
* change version
* bump fumpt version
* skip strings.title test
* go mod tidy
* update tests as some aren't private??
* update tests
This ensures the tools only run in the versions we've tested and it also
does not polute PATH with those tools so they are truly isolated. This
syntax of `go run` requires go 1.17, so the minimum version is set
accordingly.
Fixes: https://github.com/go-gitea/gitea/issues/18867
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Refactor repo-legacy.js, remove messy global variables. Fix errors.
Fix an error in Sortable
Fix a incorrect call assignMenuAttributes from the template
- Don't package node_modules in tarballs, they are not cross-platform
anymore and npm cache should not be messed with directly. Instead,
require an internet connection to rebuild the UI, which is not necessary
in the general use case because prebuilt UI files are shipped in the
public directory.
- Simplify the fomantic build and make the target phony. We don't need
anything more for something that is rarely ran.
- Use regular tar again to build tarballs and add variable for excludes
- Disable annoying npm update notifications
Fixes: https://github.com/go-gitea/gitea/pull/14578
Fixes: https://github.com/go-gitea/gitea/pull/15256
Fixes: https://github.com/go-gitea/gitea/pull/15262
Co-authored-by: 6543 <6543@obermui.de>
- Add basic frontend unit testing infrastructure using jest in ESM mode
- Rename 'make test' to 'make test-backend'
- Introduce 'make test-frontend' and 'make test' that runs both
- Bump Node.js requirement to v12. v10 will be EOL in less than a month.
- Convert all build-related JS files to ESM.
I opted to run frontend tests run as part of the compliance pipeline because
they complete fast and are not platform-specific like the golang tests.
* Consolidate Logos and update README header
- Remove unused `logo-lg.png`, `logo-sm.png` and `logo-192.png`.
- Consolidate `favicon.svg` and `logo.svg` to just `logo.svg`.
- Remove Safari Mask icon, it seems to work fine with just `favicon.png` (no SVG support).
- Remove Fluid Icon. It only served Firefox and SVG works just fine there.
- Update customization instructions.
- Update README.md to use SVG icon, increase logo size and center it and badges.
* Update README_ZH.md
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Update README_ZH.md
Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Originally, the tabbed content under 'If pre-built frontend files are present it is possible to only build the backend:‘ has tab within the tabbed content. This commit fixed it.
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Also adjusted other version mentions so go version is always mentioned
as major.minor and node only as major.
Co-authored-by: silverwind <me@silverwind.io>
* Add frontend/backend make targets, fix source release
- Add 'make backend' and 'make frontend' make targets which are used to
build go and js/css/svg files respectively.
- The 'backend' target can be invoked without requiring Node.js to be
present on the system if pre-built frontend assets are present like
in the release source tarballs.
- Fix source releases missing 'dist' folders inside 'node_modules' which
were erronously excluded from tar.
- Store VERSION in file VERSION for the release tarballs and prefer that
file over git-derived version.
* fix release task
* fix typo
* fix another typo
* Update documentation for the go module era
use go env instead of $GOPATH
Update instructions to just use git clone
Slight update to readme
Signed-off-by: Andrew Thornton <art27@cantab.net>
* fixup
* Apply suggestions from code review
Co-Authored-By: Antoine GIRARD <sapk@users.noreply.github.com>
Co-Authored-By: Bagas Sanjaya <bagasdotme@gmail.com>
* Apply suggestions from code review
* Fix GOPATH settings
Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>
Co-authored-by: Bagas Sanjaya <bagasdotme@gmail.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Remove more explicit 'generate' calls
`generate` is now implicit during `build` since #9114, it is no longer
necessary or desired to specify it explicitely.
* add js,css,generate dependencies to release task
* remove generate warning as per @lunny
* use relative instead of absolute paths
* update badges of ZH readme
* update screenshots
* use <style> for table
* remove useles stype
* absolute paths for images
