aboutsummaryrefslogtreecommitdiffstats
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* Remove `deps-tools` from `backend` job (#25454)silverwind2023-06-221-1/+1
|
* add `test-frontend` back to actions (#25452)silverwind2023-06-221-0/+1
| | | | Apparently we were not running `test-frontend` on actions, this adds it back.
* Use Actions git context instead of dynamically created buildkit one (#25381)techknowlogick2023-06-201-0/+2
| | | | | | | | | | The [docker/build-push-action@v2 action](https://github.com/docker/build-push-action) by default ignores the checkout created using the actions/checkout@v2 action. When you pass a git build context to docker build, it wouldn't include the .git directory. By passing `context: .` to the build step then it'll use the Actions git context which includes the git fetch from the earlier step.
* Fetch all git data for embedding correct version in docker image (#25361)techknowlogick2023-06-191-0/+3
| | | Fix #25350
* Only run `docker-dryrun` when necessary (#25329)silverwind2023-06-182-8/+21
| | | | | | | | | `docker-dryrun` runs on almost any PR, which is a huge waste of CI resources. Run it only when the Dockerfiles change and also add a step that verifies the rootless file. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Clean up pyproject.toml and package.json, fix poetry options (#25327)silverwind2023-06-181-0/+1
| | | | | | | | | | | | - Reduce `pyproject.toml` and `package.json` to the minimal required format, removing unneeded properties. `build-system` is not needed as per [this](https://github.com/python-poetry/poetry/issues/8110#issuecomment-1595846841). - Fix `poetry.toml` options they were wrong previously. - Add dependencies of poetry files to templates `files-changed`. --------- Co-authored-by: Giteabot <teabot@gitea.io>
* build nightly docker images (#25317)techknowlogick2023-06-181-2/+30
| | | | followup of https://github.com/go-gitea/gitea/pull/25308 this time to build & push nightly docker images
* Build nightly binaries with Actions (#25308)techknowlogick2023-06-163-0/+61
| | | Co-authored-by: silverwind <me@silverwind.io>
* Add template linting via djlint (#25212)silverwind2023-06-142-1/+21
| | | | | | | | | | | | | | | | | | 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).
* GitHub Actions enhancements for frontend (#25150)silverwind2023-06-144-21/+19
| | | | | - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
* Fix setup-go actions (#25167)silverwind2023-06-092-8/+15
| | | | | | | | | | | | | | | | | | The `setup-go` actions did not all have `check-latest` which means they use some cached version of go that currently still resolves to go1.20.4, as seen in a number of recent runs that currently fail at govulncheck because of it: ```` Run actions/setup-go@v4 Setup go version spec >=1.20 Attempting to resolve the latest version from the manifest... matching >=1.20... Resolved as '1.20.4' ```` Add the [check-latest](https://github.com/actions/setup-go#check-latest-version) option which should guarantee that this cache is skipped.
* Clean up github actions (#24984)silverwind2023-05-304-51/+59
| | | | | | | - Merge the file filters into `files-changed.yml` - Remove unused yaml anchors like `&backend` - Merge the `compliance-docs` workflow into `compliance` - Add actions linting - Misc cleanups for whitespace and step names
* Fix documentation ref (#24934)Lunny Xiao2023-05-261-0/+1
| | | Fix documentation ref
* Use file filters action instead of Github's files filter (#24877)Lunny Xiao2023-05-2511-122/+92
| | | | | | | | | | | | | | | Inspired by https://github.com/go-gitea/gitea/pull/24530#issuecomment-1558815301 This PR use a file filter action to do different CI jobs according changed files types. All types are defined in `.github/file-filters.yml`. Now there are 4 types, `docs`, `backend`, `frontend` and `build`. Then if a PR only changed docs files, those CI jobs which passed the conditions will run, and other types are also like this. --------- Co-authored-by: silverwind <me@silverwind.io>
* Remove publish docs CI workflow (#24889)techknowlogick2023-05-231-29/+0
| | | | Now that the redirect to docs.gitea.com is in place this is no longer needed.
* replace `drone exec` to `act_runner exec` in test README.md (#24791)a10121127962023-05-181-5/+5
|
* Ignore build for docs only (#24761)Lunny Xiao2023-05-171-0/+30
| | | Fix https://github.com/go-gitea/gitea/pull/24530#issuecomment-1550227919
* Don't run build and test if only docs changed (#24530)Lunny Xiao2023-05-1611-5/+101
| | | Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Update cron-translations.yml (#24708)Lunny Xiao2023-05-141-0/+1
| | | Fix cron translations push failure
* fix minio storage iterator path (#24691)FuXiaoHei2023-05-131-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | minio storage iterator shows different behavior with local fs iterator. in local fs storage: ``` go s.IterateObjects("prefix", func(path,obj) println(path) // show "prefix/xxx.file" }) ``` in minio storage: ```go s.IterateObjects("prefix", func(path,obj) println(path) // show "xxx.file" }) ``` I think local fs is correct, minio use wrong `basePath` to trim storage path prefix. --------- Co-authored-by: Giteabot <teabot@gitea.io>
* GitHub Actions cleanups (#24620)silverwind2023-05-1112-286/+171
| | | | | | | | | | - Remove actions name where command is descriptive enough - Use kebab-case instead of snake-case for step names - Use shorter job names because to make PR checks more readable - Remove duplicate `checks-backend` --------- Co-authored-by: Yarden Shoham <git@yardenshoham.com>
* Kd/fix redis unit test (#24650)Kyle D2023-05-111-0/+10
| | | | | | | | | Replaces #24641 Currently, unit tests fail when run locally (unless users have minio instance running). This PR only requires redis unit tests if in CI. - Only run redis unit tests when `CI` env variable is set - Add minio as a service in unit tests actions
* Check latest version on CI (#24556)Lunny Xiao2023-05-062-0/+6
|
* automate locking closed threads (#24525)techknowlogick2023-05-052-23/+21
| | | | | | | | | With comments happening on closed issues/prs this locks issues that have been closed for >45days. This allows for comments on recently closed issues/prs to still happen. --------- Co-authored-by: silverwind <me@silverwind.io>
* Upgrade to Node 20 on CI, enable actions cancellation (#24524)silverwind2023-05-045-5/+25
| | | | | | | | | | | | - Upgrade node, the [snap](https://github.com/go-gitea/gitea/blob/7abe958f5b507efa676fb3b2e27d30517f6d1908/snap/snapcraft.yaml#L47) is excluded from this because [there is no Node 20 snap yet](https://snapcraft.io/node). - Add actions build cancellation based on [this](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-a-fallback-value). --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Use Actions for DB & E2E tests (#24494)techknowlogick2023-05-048-7/+428
| | | | | | | | | | following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
* replace PR docker dry run in drone with Actions (#24475)techknowlogick2023-05-011-0/+19
| | | | | | | | As before with past PRs to switch Drone pipelines to use (GitHub) Actions. --------- Co-authored-by: silverwind <me@silverwind.io>
* correct env varstechknowlogick2023-05-011-1/+1
|
* target correct conditionaltechknowlogick2023-05-011-2/+2
|
* Move docs pipelines to use Actions (#24434)techknowlogick2023-04-302-0/+53
| | | | | | | | similar to #24314, this moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. I also removed the discord notify pipeline, as it hasn't been working for several months.
* on scheduletechknowlogick2023-04-251-1/+1
|
* on scheduletechknowlogick2023-04-251-1/+1
|
* switch to use Actions from drone for cron (#24314)techknowlogick2023-04-252-0/+75
| | | | | Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
* Improve pull_request_template.md (#22888)Jason Song2023-02-201-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update `pull_request_template.md` because: - It's a kind idea to hide the tips. However, it's easier to include them in the commit message by mistake when you cannot see them. Check `git log | grep 'Please check the following:'`. So don't hide it, expose it and help fix it. - "for backports" is much clearer than "for bug fixes". I saw someone post a PR to a release branch because they believed it was the right way for a bugfix. - "Allow edits by maintainers", or we have to ask the contributor to update the branch and they could be confused. - Remind the contributor that the words could be included in the commit message, to avoid some words like "Hello", "Sorry". If they really need them, they can separate them with a line, like: ```markdown Close #xxxx Because ... Then ... Finally ... --- Hello, this is my first time opening a pull request. Sorry for any mistakes. ``` And the merger should be careful, check and delete the extra content before merging. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* update discord invite (#19907)Eugene2022-06-071-1/+1
|
* Disable blank issues (#19717)John Olheiser2022-05-151-1/+1
|
* Reorder issue templates and automatically add labels (#18875)delvh2022-03-213-57/+60
| | | | | | | | | | | | | | | * Reorder bug-report.yaml * Add bug label on bug-report.yaml * Add feature label on feature-request.yaml * Reorder ui.bug-report.yaml * Apply suggestions Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: zeripath <art27@cantab.net>
* Make the proformas clearer that we need DEBUG logs (#18700)zeripath2022-02-102-0/+6
| | | | | | | | | | It is ridiculous how few of our bug reporter are giving us DEBUG level logs. This has to change and I think the proforma is not making it clear enough that they have to give us these logs. This PR changes the issue proformas to tell people to give us these logs. Signed-off-by: Andrew Thornton <art27@cantab.net>
* Fix documents for development and bug report (#18249)wxiaoguang2022-01-131-8/+9
|
* Fix various typos of software names (#18083)qwerty2872021-12-241-1/+1
| | | | | | | | | | | | | | | | * `git` -> `Git` * `Github` and `github` -> `GitHub` * `crowdin` -> `Crowdin` * `git-lfs` -> `Git LFS` * `githooks`, `git hooks`, `git-hooks` -> `Git Hooks` * `discord` -> `Discord` * `2fa` -> `2FA` * `gitlab` and `Gitlab` -> `GitLab` * `web hook` -> `webhook` * `linux` -> `Linux` * `sqlite` -> `SQLite` * `MYSQL` and `mysql` -> `MySQL` * rename refs to `master` branch -> `main` * Fix English grammar
* hide note message for pull request template (#17529)a10121127962021-11-021-1/+3
| | | Co-authored-by: John Olheiser <john.olheiser@gmail.com>
* Fix wording in issue template (#17176)silverwind2021-09-291-1/+1
| | | There was a typo `systemm` here. I opted to just remove the superfluos word altogether.
* Issue template form (#16349)Gabriel2021-09-155-42/+191
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Create issue template using new format This issue template has been based off of the current issue creation workflow defined in the ISSUE_TEMPLATE.md file This commit allows for that issue template (which is a legacy method of creating an issue) to be deleted * Delete old issue template file This commit deletes the old issue template file, as it is both legacy and replaced by ISSUE_TEMPLATE/issue.yaml * Adjust file upload and remove code of conduct checkbox * Block blank issue creation * Update feedback Removed most requirements Updated prompt to include instruction to state whether using try.gitea.io Added default value to Gitea version * Create Feature Request issue form * Update and rename issue.yaml to bug-report.yaml * Enable blank issue creation Co-authored-by: a1012112796 <1012112796@qq.com> * Update config.yaml * Remove default & placeholder from Gitea version * Create issue template in .gitea directory * Add relevant bug report message to feature request * Adjust name to remove banner There is a banner that tells you to create a config.yml when you already have a config.yaml Renaming the file stops this from occurring. * Add UI bug report form * Remove unnecessary question Co-authored-by: a1012112796 <1012112796@qq.com> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv>
* Update pull_request_template.md (#15948)Ikko Ashimine2021-05-221-1/+1
| | | | Branch name - master -> main
* Issue template addition: Are you using Gitea behind CloudFlare? (#14098)wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf2021-02-181-0/+3
| | | | | | | | | | | | | | | | | | | | * chore: are you using Gitea behind CloudFlare since more often than not CF appears to serve stale cache and cause troubles, I'd argue it might be helpful to ask about it in this here issue template * implement suggestion: change question to comment * as per @techknowlogick's suggestion * chore: edit comment * implement @mrsdizzie's suggestion * as the comment grows, rather span multiple lines * Gitea --> gitea to match case used in the rest of the template Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Kd/add bountysource (#14323)Kyle D2021-01-131-0/+1
| | | | | * Add bountysource to Sponsors link * Add badge to readme
* Add FAQ link to Issue template (#14020)65432020-12-161-2/+3
|
* Config lock bot (#13624)65432020-11-181-0/+23
| | | | | * config lock bot * Update .github/lock.yml
* add more clarification to the issue-template.md (#13235)zeripath2020-10-211-0/+6
| | | | | Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Remove not relevant option from issue template (#13188)mrsdizzie2020-10-171-1/+0
| | | | | | | Almost every use of "Not relevant" I see is the opposite -- it is relevant to have an example on try.gitea.io and often we can't do anything until the user provides one. Remove the not-relevant option so people have to decide yes/no if they are going to attempt to reproduce it which will hopefully encourage them to do so in simple cases. For actual not-relevant issues No should be a fine answer as well as it would be clear to us when you can't reproduce an example there. Hopefully this will encourage more examples when people file issues which would lead to quicker fixes.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-30 22:32:43 +0000