Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Create docker-image.yml #40368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Create docker-image.yml #40368

wants to merge 1 commit into from
+19 −0

Conversation

mikesalaZa
Copy link

@mikesalaZa mikesalaZa commented Sep 13, 2025 •
edited
Loading 

        - nombre: Análisis de composición de aplicaciones de SecureStack

Puedes anclar al commit exacto o a la versión.

usos: SecureStackCo/actions-code@c2c3584

usos: SecureStackCo/[email protected]
con:
# Clave API de SecureStack: genere una clave API en https://app.securestack.com
clave de API de securestack:
# ID de aplicación SecureStack: se puede recuperar accediendo a la aplicación requerida en https://app.securestack.com
id de la aplicación securestack:
# Las severidades inferiores a este valor se informarán en la consola de flujo de trabajo, pero no causarán un error para la acción; el valor debe ser uno de los siguientes: crítico | alto | medio | bajo
gravedad:
# Las severidades inferiores a este valor se informarán en la consola de flujo de trabajo, pero no causarán un error para la acción; el valor debe ser uno de los siguientes: crítico | alto | medio | bajo
idioma:
# Banderas opcionales para el comando bloodhound-cli code: ejecute bloodhound cli code --help para obtener más detalles
banderas: # opcional, el valor predeterminado es

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@mikesalaZa
Create docker-image.yml
a46dfbd 
            - nombre: Análisis de composición de aplicaciones de SecureStack
  # Puedes anclar al commit exacto o a la versión.
  # usos: SecureStackCo/actions-code@c2c3584
  usos: SecureStackCo/[email protected]
  con:
    # Clave API de SecureStack: genere una clave API en https://app.securestack.com
    clave de API de securestack:
    # ID de aplicación SecureStack: se puede recuperar accediendo a la aplicación requerida en https://app.securestack.com
    id de la aplicación securestack:
    # Las severidades inferiores a este valor se informarán en la consola de flujo de trabajo, pero no causarán un error para la acción; el valor debe ser uno de los siguientes: crítico | alto | medio | bajo
    gravedad:
    # Las severidades inferiores a este valor se informarán en la consola de flujo de trabajo, pero no causarán un error para la acción; el valor debe ser uno de los siguientes: crítico | alto | medio | bajo
    idioma:
    # Banderas opcionales para el comando bloodhound-cli code: ejecute bloodhound cli code --help para obtener más detalles
    banderas: # opcional, el valor predeterminado es
@github-actions GitHub Actions
Copy link
Contributor

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

  • .github/workflows/docker-image.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:

The complete list of files we can't accept are:

  • .devcontainer/**
  • .github/**
  • data/reusables/rai/**
  • Dockerfile*
  • src/**
  • package*.json
  • content/actions/how-tos/security-for-github-actions/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai or contentType: rai.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Sep 13, 2025
@github-actions GitHub Actions
Copy link
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
triage Do not begin working on this issue until triaged by the team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@mikesalaZa