github/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2026-02-13 21:00:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

cspell lint docs (#3787)

Browse Source 
Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
This commit is contained in:
6543
2024-07-22 20:42:00 +02:00
committed by GitHub
parent 251129a29c
commit c8411d7f83
41 changed files with 177 additions and 100 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/versioned_docs/version-2.7/30-administration/00-getting-started.md
View File

@@ -1,4 +1,4 @@
# Gettings started
# Getting started
A Woodpecker deployment consists of two parts:
@@ -45,7 +45,7 @@ By default Woodpecker uses a SQLite database which requires zero installation or
## Forge
What would be a CI/CD system without any code? By connecting Woodpecker to your [forge](../20-usage/15-terminology/index.md) like GitHub or Gitea you can start running pipelines on events like pushes or pull requests. Woodpecker will also use your forge for authentication and to report back the status of your pipelines. See the [forge settings](./11-forges/11-overview.md) to conntect it to Woodpecker.
What would be a CI/CD system without any code? By connecting Woodpecker to your [forge](../20-usage/15-terminology/index.md) like GitHub or Gitea you can start running pipelines on events like pushes or pull requests. Woodpecker will also use your forge for authentication and to report back the status of your pipelines. See the [forge settings](./11-forges/11-overview.md) to connect it to Woodpecker.
## Configuration