mirrors/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2024-11-26 11:51:02 +00:00
Code Issues Projects Releases Wiki Activity

docs: Fix spelling (#3887)

Browse source 
Co-authored-by: finga <finga@onders.org>
This commit is contained in:
finga 2024-07-12 14:57:30 +02:00 committed by GitHub
parent ca6e21d654
commit 388f14185c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/docs/92-development/01-getting-started.md
View file

@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
### Create a `.env` file with your development configuration ### Create a `.env` file with your development configuration
Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it. Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
A common config for debugging would look like this: A common config for debugging would look like this:

2
docs/versioned_docs/version-1.0/92-development/01-getting-started.md
View file

@ -39,7 +39,7 @@ For dependencies installation (node_modules) for the UI and documentation of Woo
### Create a `.env` file with your development configuration ### Create a `.env` file with your development configuration
Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it. Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
A common config for debugging would look like this: A common config for debugging would look like this:

2
docs/versioned_docs/version-2.4/92-development/01-getting-started.md
View file

@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
### Create a `.env` file with your development configuration ### Create a `.env` file with your development configuration
Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it. Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
A common config for debugging would look like this: A common config for debugging would look like this:

2
docs/versioned_docs/version-2.5/92-development/01-getting-started.md
View file

@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
### Create a `.env` file with your development configuration ### Create a `.env` file with your development configuration
Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it. Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
A common config for debugging would look like this: A common config for debugging would look like this:

2
docs/versioned_docs/version-2.6/92-development/01-getting-started.md
View file

@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
### Create a `.env` file with your development configuration ### Create a `.env` file with your development configuration
Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it. Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
A common config for debugging would look like this: A common config for debugging would look like this: