2021-06-22 12:34:35 +02:00
|
|
|
### IDEs ###
|
|
|
|
|
.idea/
|
2021-12-21 05:45:41 +02:00
|
|
|
.vscode/*
|
2021-12-21 11:52:10 +02:00
|
|
|
!.vscode/settings.json
|
2021-06-22 12:34:35 +02:00
|
|
|
!.vscode/launch.json
|
2021-12-21 05:45:41 +02:00
|
|
|
!.vscode/extensions.json
|
2021-06-22 12:34:35 +02:00
|
|
|
|
|
|
|
|
### GO ###
|
|
|
|
|
# Binaries for programs and plugins
|
|
|
|
|
*.exe
|
|
|
|
|
*.exe~
|
|
|
|
|
*.dll
|
|
|
|
|
*.so
|
|
|
|
|
*.dylib
|
2022-06-17 01:57:02 +02:00
|
|
|
vendor/
|
2024-04-26 13:46:55 +02:00
|
|
|
__debug_bin*
|
2021-06-22 12:34:35 +02:00
|
|
|
|
|
|
|
|
# Test binary, built with `go test -c`
|
|
|
|
|
*.test
|
|
|
|
|
|
|
|
|
|
# Output of the go coverage tool, specifically when used with LiteIDE
|
|
|
|
|
*.out
|
|
|
|
|
|
|
|
|
|
### Frontend ###
|
2021-09-29 17:34:56 +02:00
|
|
|
web/dist/**
|
|
|
|
|
!web/dist/.gitkeep
|
|
|
|
|
web/node_modules/
|
2021-06-22 12:34:35 +02:00
|
|
|
web/*.log
|
|
|
|
|
web/.env
|
Use consistent woodpecker color scheme (#2003)
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079
What do you think about using a consistent `woodpecker` color scheme?
Right now, the `lime` color scheme from windicss is used that does not
really fit the primary color used for the documentation website. I have
used the primary color `#4CAF50` from the docs and created a color
palette with https://palettte.app/:
<details>
<summary>JSON source</summary>
```Json
[
{
"paletteName": "New Palette",
"swatches": [
{
"name": "New Swatch",
"color": "166E30"
},
{
"name": "New Swatch",
"color": "248438"
},
{
"name": "New Swatch",
"color": "369943"
},
{
"name": "New Swatch",
"color": "4CAF50"
},
{
"name": "New Swatch",
"color": "68C464"
},
{
"name": "New Swatch",
"color": "8AD97F"
}
]
}
]
```
</details>
I have added this color scheme to the windicss config and replaced the
use of `lime` in the UI. While `woodpecker-300` would be the primary
color that is used for the docs, I currently use `woodpecke-400` as
primary color for the UI to fix some contrast issues.
What do you think? If you would like to stay with the current colors,
that's fine for me, I can just use the custom CSS feature in this case.
---------
Co-authored-by: 6543 <6543@obermui.de>
2023-08-02 09:09:12 +02:00
|
|
|
.pnpm-store
|
2021-06-22 12:34:35 +02:00
|
|
|
|
|
|
|
|
### Docker ###
|
|
|
|
|
docker-compose.yml
|
|
|
|
|
|
|
|
|
|
### Other ##
|
|
|
|
|
# runetime or build relicts
|
2014-02-07 13:10:01 +03:00
|
|
|
*.sqlite
|
2015-09-30 03:21:17 +02:00
|
|
|
*.out
|
2019-04-26 13:46:06 +02:00
|
|
|
/.env
|
2017-05-08 02:01:04 +02:00
|
|
|
extras/
|
2021-09-21 16:36:41 +02:00
|
|
|
/build/
|
2021-10-04 19:50:21 +02:00
|
|
|
/dist/
|
2023-12-28 17:39:14 +02:00
|
|
|
/data/
|
2024-04-02 10:10:29 +02:00
|
|
|
datastore/migration/testfiles/
|
2015-10-23 02:03:07 +02:00
|
|
|
|
2019-11-13 13:23:16 +02:00
|
|
|
docs/venv
|
2022-01-24 12:41:39 +02:00
|
|
|
|
|
|
|
|
# helm charts
|
|
|
|
|
.cr-index/
|
|
|
|
|
.cr-release-packages/
|
2022-09-27 22:19:39 +02:00
|
|
|
|
|
|
|
|
### Generated by CI ###
|
|
|
|
|
docs/docs/40-cli.md
|
2024-11-23 10:17:19 +02:00
|
|
|
docs/openapi.json
|
|
|
|
|
|
|
|
|
|
# Removed once v3.0.x is minimum version to be touched
|
2023-06-04 05:07:39 +02:00
|
|
|
docs/swagger.json
|
