Beyond coding. We forge. https://forgejo.org
Find a file
Giteabot 5099d3c747
Set pre-step status to skipped if job is skipped (#29489) (#29523)
Backport #29489 by @sillyguodong

close #27496
1. Set pre-step (Set up job) status to `skipped` if job is skipped.
2. Apart from pre-step, the other steps should also be set to `skipped`.
The status of other steps are reported from the runner side. This will
be completed by this PR: https://gitea.com/gitea/act_runner/pulls/500

before:

![image](https://github.com/go-gitea/gitea/assets/33891828/4bac2ba9-66de-4679-b7ed-fbae459c0c54)

after:

![image](https://github.com/go-gitea/gitea/assets/33891828/ead4871a-4e0f-4bb1-9fb4-37f4fdb78dfc)

Co-authored-by: sillyguodong <33891828+sillyguodong@users.noreply.github.com>
(cherry picked from commit 8d085587831d1357ae80046fe0627dbcc8657a79)
2024-03-10 18:45:58 +07:00
.devcontainer
.forgejo Revert "[CI] pin go v1.21.8 version" 2024-03-06 12:18:06 +08:00
.gitea [WORKFLOW] yaml issue templates 2023-11-13 12:33:49 +01:00
.github Fix Docker meta action for releases (#28232) (#28395) 2023-12-08 13:41:16 +01:00
assets [GITEA] Use maintained gziphandler 2024-01-16 14:09:55 +00:00
build [I18N] Add Locale merger script (squash) abort on NOOP 2023-11-28 17:52:11 +01:00
cmd Merge pull request '[BUG] Initialize Git for hook regeneration' (#2421) from gusted/forgejo-bp-2416 into v1.21/forgejo 2024-02-21 14:41:45 +00:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-11-13 14:00:15 +01:00
custom/conf Refactor CORS handler (#28587) (#28611) 2024-01-16 14:08:38 +00:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-11-13 13:58:17 +01:00
docs Improve frontend guideline (#28711) (#28713) 2024-01-16 14:16:56 +00:00
models [BUG] Ensure HasIssueContentHistory takes into account comment_id 2024-03-01 15:48:42 +01:00
modules Set pre-step status to skipped if job is skipped (#29489) (#29523) 2024-03-10 18:45:58 +07:00
options Fix validity of the FROM email address not being checked (#29347) (#29360) 2024-03-06 12:20:42 +08:00
public [BRANDING] security.txt 2023-11-13 14:01:11 +01:00
releases/images
routers Fix missed return (#29450) (#29453) 2024-03-10 18:08:05 +07:00
services The job should always run when if is always() (#29464) (#29469) 2024-03-10 18:08:15 +07:00
snap
templates Fix URL calculation in clone input box (#29470) (#29473) 2024-03-10 18:08:36 +07:00
tests Merge pull request '[BUG] prevent removing session cookie when redirect_uri query contains ://' (#2606) from oliverpool/forgejo:backport2590 into v1.21/forgejo 2024-03-08 15:07:50 +00:00
web_src Improve contrast on blame timestamp, fix double border (#29482) (#29485) 2024-03-10 18:45:58 +07:00
.air.toml
.changelog.yml
.dockerignore
.editorconfig
.eslintrc.yaml Fix gitea-origin-url with default ports (#29085) (#29088) 2024-02-13 14:17:58 +01:00
.gitattributes
.gitignore [I18N] Makefile + gitignore 2023-11-13 13:57:47 +01:00
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml
BSDmakefile
build.go
CHANGELOG.md Add changelog for 1.21.4 (#28812) 2024-01-31 13:35:57 +01:00
CODEOWNERS [META] Add CODEOWNERS files 2023-11-13 12:33:49 +01:00
CONTRIBUTING.md
DCO
Dockerfile [CI] Forgejo Actions based release process (squash) gitea to forgejo 2023-11-13 13:58:18 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process (squash) gitea to forgejo 2023-11-13 13:58:18 +01:00
go.mod bump protobuf module (#29617) 2024-03-06 11:53:02 +08:00
go.sum bump protobuf module (#29617) 2024-03-06 11:53:02 +08:00
LICENSE
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-11-13 13:58:18 +01:00
MAINTAINERS
Makefile [SEMVER] 6.0.7+0-gitea-1.21.7 2024-03-06 13:05:29 +08:00
package-lock.json Bump @github/relative-time-element to 4.3.1 (#28819) (#28826) 2024-01-31 13:36:02 +01:00
package.json Bump @github/relative-time-element to 4.3.1 (#28819) (#28826) 2024-01-31 13:36:02 +01:00
playwright.config.js
poetry.lock
poetry.toml
pyproject.toml [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-11-13 13:58:17 +01:00
README.md [BRANDING] add Forgejo logo 2023-11-13 13:58:17 +01:00
RELEASE-NOTES.md
vitest.config.js
webpack.config.js

Welcome to Forgejo

Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.

Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!

What does Forgejo offer?

If you like any of the following, Forgejo is literally meant for you:

  • Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
  • Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
  • Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
  • Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
  • Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
  • Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
  • Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances.

Learn more

Dive into the documentation, subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.

Get involved

If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.