fix: use forgejo.repository for aikido full scan schedule compatibility
All checks were successful
validate-shared-actions / validate-shared-actions (pull_request) Successful in 38s
Aikido Security PR Check / Aikido Security Scan (pull_request) Successful in 2m4s

forgejo.event.repository.name is absent on schedule triggers.
forgejo.repository is always set to 'owner/repo' regardless of trigger type.
This commit is contained in:
Michael.Seele@schmalz.de 2026-05-21 07:37:05 +00:00
parent 74aa5eb12f
commit 44164494c8
2 changed files with 3 additions and 8 deletions

View file

@ -15,6 +15,5 @@ runs:
- uses: https://schmalz-git.git.onstackit.cloud/schmalz/shared-actions/internal-aikido-full-scan@internal-aikido-full-scan-v1
with:
apikey: ${{ inputs.apikey }}
organization: ${{ forgejo.repository_owner }}
repository-name: ${{ forgejo.event.repository.name }}
repository-name: ${{ forgejo.repository }}
branch-name: ${{ forgejo.ref_name }}

View file

@ -5,11 +5,8 @@ inputs:
apikey:
description: Aikido CI API key
required: true
organization:
description: Organization or owner name
required: true
repository-name:
description: Repository name
description: Full repository name (owner/repo)
required: true
branch-name:
description: Branch to scan against
@ -23,9 +20,8 @@ runs:
- --apikey
- ${{ inputs.apikey }}
- --repositoryname
- ${{ inputs.organization }}/${{ inputs.repository-name }}
- ${{ inputs.repository-name }}
- --branchname
- ${{ inputs.branch-name }}
- --force-create-repository-for-branch
- --include-dev-deps