docs: update docs

This commit is contained in:
sebthom 2025-10-17 20:51:23 +02:00
parent 43ec328ba8
commit 6f10cdfa3d
5 changed files with 179 additions and 179 deletions

View File

@ -3,12 +3,12 @@
# SPDX-License-Identifier: Apache-2.0 # SPDX-License-Identifier: Apache-2.0
# SPDX-ArtifactOfProjectHomePage: https://github.com/vegardit/docker-gitea-act-runner # SPDX-ArtifactOfProjectHomePage: https://github.com/vegardit/docker-gitea-act-runner
# #
# https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions # https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
name: Build name: Build
on: # https://docs.github.com/en/actions/reference/events-that-trigger-workflows on: # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows
schedule: schedule:
# https://docs.github.com/en/actions/reference/choosing-when-your-workflow-runs/events-that-trigger-workflows # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule
- cron: '0 17 * * 3' - cron: '0 17 * * 3'
push: push:
branches-ignore: # build all branches except: branches-ignore: # build all branches except:
@ -35,7 +35,7 @@ on: # https://docs.github.com/en/actions/reference/events-that-trigger-workflow
- '.github/ISSUE_TEMPLATE/*' - '.github/ISSUE_TEMPLATE/*'
- '.github/workflows/stale.yml' - '.github/workflows/stale.yml'
workflow_dispatch: workflow_dispatch:
# https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#workflow_dispatch
inputs: inputs:
VERSION: VERSION:
type: string type: string

View File

@ -1,12 +1,12 @@
# https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions # https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
name: Stale issues name: Stale issues
on: on: # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows
schedule: schedule:
# https://docs.github.com/en/actions/reference/events-that-trigger-workflows # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule
- cron: '0 15 1,15 * *' - cron: '0 15 1,15 * *'
workflow_dispatch: workflow_dispatch:
# https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#workflow_dispatch
permissions: permissions:
issues: write issues: write

View File

@ -60,7 +60,7 @@ representative at an online or offline event.
Instances of abusive, harassing, or otherwise unacceptable behavior may be Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at reported to the community leaders responsible for enforcement at
https://vegardit.com/en/legal/ https://vegardit.com/legal/
All complaints will be reviewed and investigated promptly and fairly. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the All community leaders are obligated to respect the privacy and security of the

View File

@ -30,7 +30,7 @@ We use GitHub Issues to track bugs and feature requests. When submitting an issu
Before making substantial contributions: Before making substantial contributions:
1. **Discuss Changes**: Please file an issue first to discuss your proposed changes with the team. This helps ensure your contribution aligns with the projects goals. 1. **Discuss Changes**: Please file an issue first to discuss your proposed changes with the team. This helps ensure your contribution aligns with the projects goals.
2. **Follow Best Practices**: Adhere to the guidelines and ensure your code meets the projects standards (see [Code Guidelines](#code-guidelines)). 2. **Follow Best Practices**: Adhere to the guidelines and ensure your code meets the projects standards.
When submitting a pull request: When submitting a pull request:
- Ensure your changes are well-documented. - Ensure your changes are well-documented.