Skip to content

Conversation

@edwinguillermoarroyogarcia-tech
Copy link

@edwinguillermoarroyogarcia-tech edwinguillermoarroyogarcia-tech commented Feb 9, 2026

De ce:

Închide:

Qué se está cambiando (si está disponible, incluya fragmentos de código, capturas de pantalla o gifs):

Comprueba lo siguiente:

  • Un experto en la materia (PYME) ha revisado la precisión técnica del contenido de este PR. En la mayoría de los casos, el autor puede ser la PYME. Las contribuciones de código abierto pueden requerir una revisión de las PYME por parte del personal de GitHub.
  • Los cambios en este PR cumplen con los fundamentos de los documentos que se requieren para todo el contenido.
  • Todas las comprobaciones de CI están pasando y los cambios se ven bien en el entorno de revisión.

pull-inactive-pull-request] $ git push origin BRANCH_NAME
> Counting objects: 32, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (26/26), done.
> Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
> Total 29 (delta 8), reused 0 (delta 0)
> To https://github.com/USERNAME/REPOSITORY.git
>  * [new branch]      BRANCH_NAME -> BRANCH_NAME
Create a new pull request with your new branch.5539377724# A first-level heading
## A second-level heading
### A third-level heading// This sample uses Atlassian Forge
// https://developer.atlassian.com/platform/forge/
import { requestConfluence } from "@forge/bridge";

const response = await requestConfluence(`/wiki/api/v2/databases/{id}`, {
  headers: {
    'Accept': 'application/json'
  }
});

console.log(`Response: ${response.status} ${response.statusText}`);
console.log(await response.json());https://github.com/USERNAME/REPOSITORY.githttps://developer.atlassian.com/platform/forge/// This sample uses Atlassian Forge
// https://developer.atlassian.com/platform/forge/
import { requestConfluence } from "@forge/bridge";

const response = await requestConfluence(`/wiki/api/v2/data-policies/spaces`, {
  headers: {
    'Accept': 'application/json'
  }
});

console.log(`Response: ${response.status} ${response.statusText}`);
console.log(await response.json());cp php_includes/config.inc.dist php_includes/config.inc
cp php_includes/cmaster.inc.dist php_includes/cmaster.inc
cp php_includes/blackhole.inc.dist php_includes/blackhole.inc
rutas de viaje:
  - identificación: 'getting_started'
    título: 'Comenzando con {% variables de datos.product.prodname_actions %}'
    descripción: 'Conozca los conceptos básicos de las acciones de GitHub.'
    guías:
      - href: '/acciones/inicio rápido'
      - href: '/acciones/aprender-github-acciones'
        alternativaSiguientePaso: '¿quieres saltar adelante? Consulte [AUTOTITLE](/actions/using-workflows).'
      - href: '/acciones/uso-flujos de trabajo'
  - identificación: 'avanzado'
    título: 'Avanzado {% variables de datos.product.prodname_actions %}'
    descripción: 'Profundice en las funciones avanzadas.'
    guías:
      - href: '/actions/using-workflows/workflow-syntax-for-github-actions'
      - href: '/acciones/implementación/implementación-con-github-acciones' 5539377724
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

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

  • src/search/edw

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 Feb 9, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

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.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@edwinguillermoarroyogarcia-tech
Copy link
Author

Cómo revisar estos cambios 👓

Gracias por tu contribución. Para revisar estos cambios, elija una de las siguientes opciones:

Un Hubber deberá implementar sus cambios internamente para revisarlos.

Tabla de enlaces de revisión
🤖 Este comentario es generado automáticamente.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant