247 Resultados de la búsqueda para "diff context"

workflows. Workflows triggered by pull_request_target events are run in the context of the base branch. Since the base branch is considered trusted, workflows

algunos ejemplos para utilizar enlaces relativos para mostrar una imagen. Context Enlace Relativo En un archivo .md de la misma rama /assets/images/electrocat

docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4 with: context: . file: ./Dockerfile platforms: ${{ matrix.platforms }} push: true outputs:

DiffSide The possible sides of a diff. Valores de DiffSide. LEFT The left side of the diff. RIGHT The right side of the diff. DiscussionCloseReason The possible

events. Some events also include additional properties that provide more context about the event resources. Refer to the specific event for details about

relacionada con los comentarios de revisión de la solicitud de extracción en el diff unificado de la misma. El tipo de actividad se especifica en la propiedad

line and startLine fields instead, which are file line numbers instead of diff line numbers Reason: We are phasing out diff-relative positioning for PR

Relative path of the file to comment on. position integer Line index in the diff to comment on. line integer Closing down notice. Use position parameter instead

quot;, "updated_at": "2008-01-14T04:33:35Z" } Get contextual information for a user Provides hovercard information. You can find out

for every submitted context must be in a success state. The required_contexts parameter allows you to specify a subset of contexts that must be success