mirrors/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-23 05:45:34 +03:00
Code Issues Projects Releases Packages Wiki Activity
forgejo/.gitignore

121 lines
1.9 KiB
Text
Raw Normal View History

[CI] gitignore: emacs backups (cherry picked from commit 5e418789d930ef8dc27bc5cb32f96350f5d64e06) (cherry picked from commit 3af6fd2ad38bfbe98ad72e20257704bced7988fa) (cherry picked from commit 6926787d67778f2a3bb2c9d79137a74b894e8b7d) (cherry picked from commit fe58e86a97d4ab0017908a55a9a1f240e241e3f8) (cherry picked from commit 5bf7ead6255889b5cc4ae81c3ce52d6d09e0aef3) (cherry picked from commit 44480ea79426581df15242d6ee7222be97709268) (cherry picked from commit 813848cebe61752568b9c28b9e912170e70bffb8) (cherry picked from commit 9c8d889e782ccaf3b3e71bd3abdc0777b2fd5cf5) (cherry picked from commit 914b1dcaf6d71354fd66c8c81121ad1f3e251e46) (cherry picked from commit 5449933efa74474273d882e7eb7c7840cc2990b0) (cherry picked from commit 67f007b8244c827bf9a9597834c8657440ce89f9) (cherry picked from commit cf93863cd2378b3f239b853ed5b7985fc342cd24) (cherry picked from commit 82177a0f667754d8234765551a4359b4b05b8086) (cherry picked from commit 3ef1fe468ac20e609b20eb7e93ed8cc2356c130a) (cherry picked from commit 305c935508cec1d4d41bac897c77f0ab80c51a7a) (cherry picked from commit 268f12c53c60d46372d448af7d5ce8cef3998d21) (cherry picked from commit 2e6c29fb2f5a3cb800b4d5881de8861f34b29fcb) (cherry picked from commit 173aa4b3b1823f4b1cf9f1e4b4c0cc7c8c07b470) (cherry picked from commit 9112b323d18317f0cf542fdbd98868a4f8382982) (cherry picked from commit 54031769ee355b4888aa4128df822ab154e4ee50) (cherry picked from commit afc287c17901c292c1b41270ceed4086c2f7faca) (cherry picked from commit 225d6f7ab7966a358e138afe7038d27b093102f4) (cherry picked from commit 41001442e35365e2e6180b4e8dade6fbd57508d7)
2023-08-22 09:20:40 +03:00
# Emacs
*~
Added a common golang gitignore
2016-11-04 15:41:28 +03:00
# Compiled Object files, Static and Dynamic libs (Shared Objects)
*.o
*.a
*.so
# Folders
_obj
_test
Add IDEA IntelliJ to .gitignore
2016-11-10 12:01:44 +03:00
# IntelliJ
.idea
Frontend refactor: move Vue related code from `index.js` to `components` dir, and remove unused codes. (#17301) * frontend refactor * Apply suggestions from code review Co-authored-by: delvh <dev.lh@web.de> * Update templates/base/head.tmpl Co-authored-by: delvh <dev.lh@web.de> * Update docs/content/doc/developers/guidelines-frontend.md Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> * fix typo * fix typo * refactor PageData to pageData * Apply suggestions from code review Co-authored-by: delvh <dev.lh@web.de> * Simply for the visual difference. Co-authored-by: delvh <dev.lh@web.de> * Revert "Apply suggestions from code review" This reverts commit 4d78ad9b0e96ca180e0823de17659a2e0814c099. Co-authored-by: delvh <dev.lh@web.de> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de>
2021-10-15 05:35:26 +03:00
# Goland's output filename can not be set manually
/go_build_*
Recommend/convert to use case-sensitive collation for MySQL/MSSQL (#28662) Mainly for MySQL/MSSQL. It is important for Gitea to use case-sensitive database charset collation. If the database is using a case-insensitive collation, Gitea will show startup error/warning messages, and show the errors/warnings on the admin panel's Self-Check page. Make `gitea doctor convert` work for MySQL to convert the collations of database & tables & columns. * Fix #28131 ## :warning: BREAKING :warning: It is not quite breaking, but it's highly recommended to convert the database&table&column to a consistent and case-sensitive collation.
2024-01-10 14:03:23 +03:00
/gitea_*
Add IDEA IntelliJ to .gitignore
2016-11-10 12:01:44 +03:00
Basic VSCode configuration for building and debugging (#2483) * Basic VSCode configuration for building and debugging * Fix building and debugging in Windows * Move to contrib folder and add instructions
2017-09-12 15:27:44 +03:00
# MS VSCode
.vscode
Ignore `__debug_bin*` which is generated by vscode when debugging (#29524) When debugging in VSCode now, the executable file generated will come with a random string attached. (cherry picked from commit 6841e58d1fae33311fa0239823def9dd8fba4c1f)
2024-03-01 17:18:35 +03:00
__debug_bin*
Basic VSCode configuration for building and debugging (#2483) * Basic VSCode configuration for building and debugging * Fix building and debugging in Windows * Move to contrib folder and add instructions
2017-09-12 15:27:44 +03:00
Added a common golang gitignore
2016-11-04 15:41:28 +03:00
*.cgo1.go
*.cgo2.c
_cgo_defun.c
_cgo_gotypes.go
_cgo_export.*
_testmain.go
[DEVELOPMENT] added /local/ to .gitignore Added `/local/` folder in `.gitignore` for developer personal files (rebuild, deploy with custom config, backups, sqlite databases, test curl query scripts, custom configs). In case of building, deploing, testing locally developer needs some folder for custom personal scripts, configs, data. `/local/` folder in project root is a good place to store all this files. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/1816 Co-authored-by: Alex Syrnikov <alex19srv@gmail.com> Co-committed-by: Alex Syrnikov <alex19srv@gmail.com> (cherry picked from commit c8138849ebecd88d62d10584195a748263de4710) (cherry picked from commit 7880660738574929184dcb787687c3de3baa2205) (cherry picked from commit cf9af01d88cf4e6429417189d52c269f9fd8efb9) (cherry picked from commit 8d1dcc9e0ec933ca99190700c99ff63106db2839) (cherry picked from commit 93dd605948635acb358960fc25563031d4aa5527) (cherry picked from commit 74972ae17f5e25c9fa141d4d667e730a95f166f9) (cherry picked from commit f76ce785782848318ba8d58336e02ef930455752) (cherry picked from commit eb3e46cd3be5408cb53e1f61dab408787b4d317d) (cherry picked from commit 5b0125591d4005c7465da21dc8a8e290858db9d4) (cherry picked from commit 31d86205d25f4fd5a5b2726eaf701a387c9f3391) (cherry picked from commit c2e62c6705a1979883d1b164118fb36360835a32)
2023-11-27 14:52:39 +03:00
# folder for project related local files
/local/
Added a common golang gitignore
2016-11-04 15:41:28 +03:00
*.exe
*.test
*.prof
Coverage reports for integration tests (#1960)
2017-06-15 12:38:33 +03:00
*coverage.out
add codecov.io service. (#2493) * add codecov.io service. Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com> * update Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com> * only PR or master branch (for coverage badge) Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com> * update Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com> * update init Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com>
2017-09-13 15:57:55 +03:00
coverage.all
Fix Benchmark tests, remove a broken one & add two new (#15250) * Benchmark Integration TESTS * CI: add benching-arm64 pipeline * BenchmarkRepo: name test case tests * Fix BenchmarkRepoBranchCommit beside Create new Branch * CI: benching use amd64 * rm total broken "BenchmarkRepo" * dont run benchmark in CI
2021-04-16 21:30:16 +03:00
cpu.out
Added a common golang gitignore
2016-11-04 15:41:28 +03:00
Validate migration files (#18203) JSON Schema validation for data used by Gitea during migrations Discussion at https://forum.forgefriends.org/t/common-json-schema-for-repository-information/563 Co-authored-by: Loïc Dachary <loic@dachary.org>
2022-01-26 12:45:51 +03:00
/modules/migration/bindata.go
/modules/migration/bindata.go.hash
Bindata is optional and over-writable on restart (#354) * Moved conf assets into options folder * Dropped old bindata * Started to integrate options bindata and accessors * Do not enforce a builtin app.ini * Replaced bindata calls with options * Dropped bindata task from makefile, it's the generate task now * Always embedd app.ini to provide sane config defaults * Use sane defaults for the configuration * Defined default value for SSH_KEYGEN_PATH * Dropped "NEVER EVER MODIFY THIS FILE" header from app.ini * Fixed new paths in latest test additions * Drop bindata with make clean task * Set more proper default values
2016-12-22 21:12:23 +03:00
/modules/options/bindata.go
Generate Bindata iff TAGS="bindata" and not up-to-date (#10004) * Only generate bindata if necessary * Only generate bindata if they are not up-to-date * generate a hash of the fileinfo and use that to keep up-to-date * Newer test is redundant * handle missing bindata and clean * Only update hash after successful write * switch to sha1 hash * Apply suggestions from code review Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
2020-01-27 04:05:38 +03:00
/modules/options/bindata.go.hash
Integrate public as bindata optionally (#293) * Dropped unused codekit config * Integrated dynamic and static bindata for public * Ignore public bindata * Add a general generate make task * Integrated flexible public assets into web command * Updated vendoring, added all missiong govendor deps * Made the linter happy with the bindata and dynamic code * Moved public bindata definition to modules directory * Ignoring the new bindata path now * Updated to the new public modules import path * Updated public bindata command and drop the new prefix
2016-11-29 19:26:36 +03:00
/modules/public/bindata.go
Generate Bindata iff TAGS="bindata" and not up-to-date (#10004) * Only generate bindata if necessary * Only generate bindata if they are not up-to-date * generate a hash of the fileinfo and use that to keep up-to-date * Newer test is redundant * handle missing bindata and clean * Only update hash after successful write * switch to sha1 hash * Apply suggestions from code review Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
2020-01-27 04:05:38 +03:00
/modules/public/bindata.go.hash
Integrate templates into bindata optionally (#314) Integrated optional bindata for the templates
2016-12-06 20:58:31 +03:00
/modules/templates/bindata.go
Generate Bindata iff TAGS="bindata" and not up-to-date (#10004) * Only generate bindata if necessary * Only generate bindata if they are not up-to-date * generate a hash of the fileinfo and use that to keep up-to-date * Newer test is redundant * handle missing bindata and clean * Only update hash after successful write * switch to sha1 hash * Apply suggestions from code review Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
2020-01-27 04:05:38 +03:00
/modules/templates/bindata.go.hash
Integrate public as bindata optionally (#293) * Dropped unused codekit config * Integrated dynamic and static bindata for public * Ignore public bindata * Add a general generate make task * Integrated flexible public assets into web command * Updated vendoring, added all missiong govendor deps * Made the linter happy with the bindata and dynamic code * Moved public bindata definition to modules directory * Ignoring the new bindata path now * Updated to the new public modules import path * Updated public bindata command and drop the new prefix
2016-11-29 19:26:36 +03:00
fix
2014-04-10 22:20:58 +04:00
*.db
*.log
Update repo's default branch when adding new files in an empty one (#25017) Fix #25014 Only API needs this fix. On the Web UI, users could only add new file on the default branch.
2023-05-31 12:07:51 +03:00
*.log.*.gz
Added a common golang gitignore
2016-11-04 15:41:28 +03:00
Stop ignoring gitea in general
2016-11-07 18:09:42 +03:00
/gitea
Add gitea-vet (#10948) * Add copyright Signed-off-by: jolheiser <john.olheiser@gmail.com> * Add gitea-vet and fix non-compliance Signed-off-by: jolheiser <john.olheiser@gmail.com> * Combine tools.go into build.go and clean up Signed-off-by: jolheiser <john.olheiser@gmail.com> * Remove extra GO111MODULE=on Signed-off-by: jolheiser <john.olheiser@gmail.com>
2020-04-05 09:20:50 +03:00
/gitea-vet
Basic VSCode configuration for building and debugging (#2483) * Basic VSCode configuration for building and debugging * Fix building and debugging in Windows * Move to contrib folder and add instructions
2017-09-12 15:27:44 +03:00
/debug
improve integration test to resue models/fixtures and store git repos with tests (#1627) * improve integration test to resue models/fixtures and store git repos with source * use gitea-integration-meta dir instead .tar.gz and cleanup every before every test * fix import package name
2017-04-28 16:23:28 +03:00
/integrations.test
Stop ignoring gitea in general
2016-11-07 18:09:42 +03:00
Extended gitignore
2016-11-05 01:21:28 +03:00
/bin
/dist
Prevent Firefox from using apple-touch-icon (#10402) * Prevent Firefox from using apple-touch-icon The opaque background does not work well in Firefox which uses the icon as a "rich icon". Prevent this by not specifying it in HTML. Real Apple devices will still request the icon on the static path. Fixes: https://github.com/go-gitea/gitea/issues/10394 Also adjust gitignore so app.ini.sample becomes searchable and fixed a variable name in app.ini.sample. * fix gitignore
2020-02-23 17:34:53 +03:00
/custom/*
Rename custom/conf/app.ini.sample to custom/conf/app.example.ini for better syntax light on editor (#11926) * Rename custom/conf/app.ini.sample to custom/conf/app.sample.ini for better syntax light on editor * rename to app.example.ini * per @6543 's comment, update all references on docs Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-06-18 06:16:59 +03:00
!/custom/conf/app.example.ini
Added a common golang gitignore
2016-11-04 15:41:28 +03:00
/data
Search bar for issues/pulls (#530)
2017-01-25 05:43:02 +03:00
/indexers
Extended gitignore
2016-11-05 01:21:28 +03:00
/log
move some scripts from 'build' to 'tools' directory, misc refactors (#29844) - Move some scripts from `build` to new `tools` dir. Eventually i would like to move all but let's do it step-by-step. - Add dir to eslint and move the files into vars. - Update docs accordingly. - While updating docs I noticed we were incorrectly having `public/img` path still in a few places. Replace those with the current `public/assets/img`. --------- Co-authored-by: Nanguan Lin <nanguanlin6@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io> (cherry picked from commit 095fdd691dd1a7d7748372cc73e7708278c80933)
2024-03-18 01:12:36 +03:00
/public/assets/img/avatar
Kd/ci playwright go test (#20123) * Add initial playwright config * Simplify Makefile * Simplify Makefile * Use correct config files * Update playwright settings * Fix package-lock file * Don't use test logger for e2e tests * fix frontend lint * Allow passing TEST_LOGGER variable * Init postgres database * use standard gitea env variables * Update playwright * update drone * Move empty env var to commands * Cleanup * Move integrations to subfolder * tests integrations to tests integraton * Run e2e tests with go test * Fix linting * install CI deps * Add files to ESlint * Fix drone typo * Don't log to console in CI * Use go test http server * Add build step before tests * Move shared init function to common package * fix drone * Clean up tests * Fix linting * Better mocking for page + version string * Cleanup test generation * Remove dependency on gitea binary * Fix linting * add initial support for running specific tests * Add ACCEPT_VISUAL variable * don't require git-lfs * Add initial documentation * Review feedback * Add logged in session test * Attempt fixing drone race * Cleanup and bump version * Bump deps * Review feedback * simplify installation * Fix ci * Update install docs
2022-09-02 22:18:23 +03:00
/tests/integration/gitea-integration-*
/tests/integration/indexers-*
/tests/e2e/gitea-e2e-*
/tests/e2e/indexers-*
/tests/e2e/reports
/tests/e2e/test-artifacts
/tests/e2e/test-snapshots
/tests/*.ini
Remove git sample files and ignore them (#24271)
2023-04-22 15:29:29 +03:00
/tests/**/*.git/**/*.sample
Use standard lessc and minify CSS using Node.js (#2337) * Use standard lessc and minify CSS using Node.js This changes the previous nonstandard `lessc` to the official one and enables CSS minification via the clean-css module. To build CSS, Node.js is required along with a `npm install` to get the tools installed locally in node_modules so there is no dependency on binaries in PATH. Benefits include: - Allows one to have a standard lessc in PATH. - Can now use command line switches on lessc. - Minified CSS brings faster page load times and also has the benefit of discouraging contributors from editing CSS directly. To build CSS, Node.js is required along with a `npm install` to get the tools installed locally based on the information in `package.json`. The 'make stylesheet' task was modified to run without condition. This makes it easier to work on the make task itself without having to delete files. Also fixes: https://github.com/go-gitea/gitea/issues/2198 * install node, npm and modules on drone * .PHONY * use 'minify' to minify CSS
2017-09-21 06:35:11 +03:00
/node_modules
Add template linting via djlint (#25212) So I found this [linter](https://github.com/Riverside-Healthcare/djlint) which features a mode for go templates, so I gave it a try and it did find a number of valid issue, like unbalanced tags etc. It also has a number of bugs, I had to disable/workaround many issues. Given that this linter is written in python, this does add a dependency on `python` >= 3.8 and `poetry` to the development environment to be able to run this linter locally. - `e.g.` prefixes on placeholders are removed because the linter had a false-positive on `placeholder="e.g. cn=Search"` for the `attr=value` syntax and it's not ideal anyways to write `e.g.` into a placeholder because a placeholder is meant to hold a sample value. - In `templates/repo/settings/options.tmpl` I simplified the logic to not conditionally create opening tags without closing tags because this stuff confuses the linter (and possibly the reader as well).
2023-06-14 21:17:58 +03:00
/.venv
remove and disable package-lock (#6969) * remove and disable package-lock Using exact versions in package.json has the same effect as lockfiles without all the troubles the lockfiles bring (different versions of package manager generating different lockfiles primarily). Ensured we only use exact versions in package.json and stopped generation of new lockfiles via .npmrc which is support by both the npm and yarn package managers. Fixes: https://github.com/go-gitea/gitea/issues/6967 * enable save-exact
2019-05-16 22:33:54 +03:00
/yarn.lock
Update JS dependencies, use Node 16 (#15804) - Update all JS dependencies to latest version - Use Node 16 on CI - Add new lint rules - Add some gitignore entries for debug files Co-authored-by: Lauris BH <lauris@nix.lv>
2021-05-13 18:12:36 +03:00
/yarn-error.log
/npm-debug.log*
Move public asset files to the proper directory (#25907) 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>
2023-07-18 19:06:43 +03:00
/public/assets/js
/public/assets/css
/public/assets/fonts
Move licenses.txt to /assets directory (#26866) Now that we have the `/assets` directory, we can put`licenses.txt` directly into it instead of incorrect `/js` path which was previously only done to avoid reserving a username. --------- Co-authored-by: Giteabot <teabot@gitea.io>
2023-09-01 17:42:33 +03:00
/public/assets/licenses.txt
Move public asset files to the proper directory (#25907) 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>
2023-07-18 19:06:43 +03:00
/public/assets/img/webpack
Remove golang vendored directory (#18277) * rm go vendor * fix drone yaml * add to gitignore
2022-01-15 02:16:05 +03:00
/vendor
Introduce esbuild on webpack (#14578) * Vendor node mods as cache; fix esbuild/fomantic offline build * Fix --exclude; use bsdtar for consistent globbing * Fall back to GNU tar; forward-compatible for APT 2.0 * Avoid having extd. attrs with bsdtar * Dependency and misc. optimizations * Remove extra code after esbuild-loader update Co-authored-by: Mike L <cl.jeremy@qq.com>
2021-04-02 03:11:04 +03:00
/web_src/fomantic/node_modules
Precompile fomantic-ui files (#13332) We rarely change fomantic-ui or its configuration so it's kind of a waste to have it rebuild on every CI run. These changes remove the fomantic files from the build and instead add the relevant output files to the git index, which should shave of 2-3 minutes on every CI run. `make fomantic` should still work and should be ran whenever fomantic is updated or its configuration is changed. Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-10-28 02:44:06 +03:00
/web_src/fomantic/build/*
!/web_src/fomantic/build/semantic.js
!/web_src/fomantic/build/semantic.css
!/web_src/fomantic/build/themes
/web_src/fomantic/build/themes/*
!/web_src/fomantic/build/themes/default
/web_src/fomantic/build/themes/default/assets/*
!/web_src/fomantic/build/themes/default/assets/fonts
/web_src/fomantic/build/themes/default/assets/fonts/*
!/web_src/fomantic/build/themes/default/assets/fonts/icons.woff2
!/web_src/fomantic/build/themes/default/assets/fonts/outline-icons.woff2
Add frontend/backend make targets, fix source release (#10325) * 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
2020-02-22 12:15:11 +03:00
/VERSION
Add 'watch-backend' (#12330) * Add 'watch-backend' This leverages `air` to watch the backend files and trigger `make backend` automatically when they change. It seems to work rather well together with `watch-frontend`. Fixes: https://github.com/go-gitea/gitea/issues/12318 * rework docs to a new section for continuous build Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-07-27 21:05:42 +03:00
/.air
Add go licenses to licenses.txt (#21034) `make go-licenses` will generate `assets/go-licenses.json` which is then included in the webpack build. This step depends on both go and node being present, so unfortunately, I could not automate the generation by hooking it up to `tidy` as that target is triggered on CI where we do not have a docker image with both go an node. It should be ran from time to time, ideally after each go mod update.
2022-09-04 01:20:46 +03:00
/.go-licenses
[DEADCODE] Add deadcode linter - Add the experimental [deacode](https://pkg.go.dev/golang.org/x/tools/internal/cmd/deadcode) linter to Forgejo. - To deal with false positives that can happen due to build tags or with code that's currently only referenced by test code, the output of the tool is compared against a known-good output. - This commit doesn't make any attempt to remove any deadcode. (cherry picked from commit ac462279e9361070326d512fc209b6f148f27865) (cherry picked from commit b5ea6e85acecb8c02d18d51ec489bb1d329a33ce) (cherry picked from commit 5915f3643c1939ab09dcac8f9fcb74bd4231a16d) [CLEANUP] Remove deadcode - This is deadcode since https://codeberg.org/forgejo/forgejo/pulls/1802 removed the usage of it. (cherry picked from commit d840b9923e1a7aad7306c6b4d02df771ed0f40f4) (cherry picked from commit 9442bab6266807141a14a647d3bc383233fc56e9) (cherry picked from commit 0de9d18863c6af44941c7021548cdb07173ba3c0) (cherry picked from commit 26abf783746ef29e66eea966160e2f9c139add26) (cherry picked from commit 05d3a143c3785f3cc5e7f561aa2ad2ba556b55cc) (cherry picked from commit 4b3d38d5e15b0fd02839d5687b634e7999e12666) (cherry picked from commit a726e7198613b330a58c8c6dfc8866c360fbe555) (cherry picked from commit cb62ae5b9885bcd5c2b6cb60f0e9cce6a991cc3c) (cherry picked from commit 8195ba06d52fc1a05e9907149bb441b66887870e) (cherry picked from commit 4570fb591aac0359a36800c8cadcd71613bdc7df) (cherry picked from commit 1f4d33de2b68c776a305fe38fe6be5ae510ce983)
2023-10-21 14:30:19 +03:00
/.cur-deadcode-out
snap-packaging for gitea (#2568) * Modify tbraeutigam/gogs-snap for gitea * Fix building on 16.04 (manually build go-bindata). -> add _source.tar.bz2 to .gitignore (used by snapcraft cleanbuild) * Streamline Snap packaging: - Take advantage of install-hooks (snapd 2.27) - Use snapctl configuration storage for unchanging values * Move to using Snap Hooks for configuration * Missed re-adding daemon statement * Fix two warnings from Codacy.
2018-05-09 17:52:51 +03:00
# Snapcraft
update snap package (#27021)
2023-09-12 15:47:53 +03:00
/gitea_a*.txt
snap-packaging for gitea (#2568) * Modify tbraeutigam/gogs-snap for gitea * Fix building on 16.04 (manually build go-bindata). -> add _source.tar.bz2 to .gitignore (used by snapcraft cleanbuild) * Streamline Snap packaging: - Take advantage of install-hooks (snapd 2.27) - Use snapctl configuration storage for unchanging values * Move to using Snap Hooks for configuration * Missed re-adding daemon statement * Fix two warnings from Codacy.
2018-05-09 17:52:51 +03:00
snap/.snapcraft/
parts/
stage/
prime/
*.snap
*.snap-build
*_source.tar.bz2
Add Node.js build dep, remove built js/css files (#9114) - Added Node.js as build dependency and removes build files from git. - Added version checks for both Go and Node.js. - Overhauled the js/css make target to only run when needed. - Merged the `generate` make target into `build` as per suggestion. Fixes: https://github.com/go-gitea/gitea/issues/6782 Fixes: https://github.com/go-gitea/gitea/issues/9216
2019-12-05 06:41:38 +03:00
.DS_Store
Use a file as make evidence for fomantic instead of a directory (#10032) * Use evidence file as dependency instead of dir * fix eol * Update .gitignore Co-Authored-By: silverwind <me@silverwind.io> * Use FOMANTIC_SOURCES to establish dependencies as per @silverwind Co-authored-by: silverwind <me@silverwind.io>
2020-02-01 23:15:32 +03:00
# Make evidence files
/.make_evidence
Generate man pages (#13901) * extend gitignore * first working draft * use docs subcomand * rm config-sheet-sheet-2-man
2021-02-25 01:36:48 +03:00
# Manpage
/man
Reference in a new issue Copy permalink