284 Suchergebnisse für "runs-on"

who-to-greet durch deinen Namen ersetzen. YAML on: [push] jobs: hello_world_job: runs-on: ubuntu-latest name: A job to say hello steps: - uses: actions/checkout@v4

issues on: schedule: - cron: "30 1 * * *" jobs: close-issues: runs-on: ubuntu-latest permissions: issues: write pull-requests: write steps: -

verwendet. YAML name: CI on: pull_request: branches: [ main ] jobs: build: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4

schedule: - cron: 20 07 * * 1 jobs: create_issue: name: Create team sync issue runs-on: ubuntu-latest permissions: issues: write steps: - name: Create team sync

# set this to an array of override file paths on: [push] jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Azure Login uses:

sollen, kannst du den Namen der Skalierungsgruppe als Wert für den runs-on-Schlüssel in deiner GitHub Actions-Workflowdatei angeben. In der folgenden Konfiguration

branches: [main] schedule: - cron: '15 5 * * 3' jobs: analyze: name: Analyze runs-on: ubuntu-latest permissions: security-events: write actions: read strategy:

von Standardoptionen für den run-Schritt für einen Auftrag jobs: job1: runs-on: ubuntu-latest defaults: run: shell: bash working-directory: ./scripts

Thursday at 15:45 UTC. on: push: schedule: - cron: '45 15 * * 4' jobs: build: runs-on: ubuntu-latest permissions: # required for all workflows security-events:

review". on: pull_request: types: - ready_for_review jobs: track_pr: runs-on: ubuntu-latest steps: # Uses the [actions/create-github-app-token](https://github