Esta versión de GitHub Enterprise Server se discontinuó el 2024-07-09. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener rendimiento mejorado, seguridad mejorada y nuevas características, actualice a la versión más reciente de GitHub Enterprise Server. Para obtener ayuda con la actualización, póngase en contacto con el soporte técnico de GitHub Enterprise.

Acerca de la automatización de projects (classic)

Puedes configurar flujos de trabajo automáticos para mantener el estado de las tarjetas del tablero de Proyecto (clásico) en sincronización con las incidencias y las solicitudes de incorporación de cambios asociadas.

En este artículo

Note

  • Projects (beta), the all-new projects experience, is now available. For more information about Projects (beta), see "About Projects (beta)."
  • You can only create a new project (classic) for an organization, repository, or user that already has at least one project (classic). If you're unable to create a project (classic), create a project instead.

To set up automatic workflows for a repository project (classic), you must have write access to the repository. Organization owners and members can configure automatic workflows on an organization-wide project (classic). For more information, see "Project (classic) permissions for an organization."

You can automate actions based on triggering events for project (classic) columns. This eliminates some of the manual tasks in managing a project (classic). For example, you can configure a "To do" column, where any new issues or pull requests you add to a project (classic) are automatically moved to the configured column. For more information, see "Configuring automation for projects (classic)."

You can use a project (classic) template to create a project (classic) with automation already configured. For more information, see "About projects (classic)."

Project (classic) automation can also help teams develop a shared understanding of a project (classic)'s purpose and the team's development process by creating a standard workflow for certain actions.

When you close a project (classic), any workflow automation configured for the project (classic) will pause. If you reopen a project (classic), you have the option to sync automation, which updates the position of the cards on the board according to the automation settings configured for the project. For more information, see "Reopening a closed project (classic)" or "Closing a project (classic)."

Automation options

Column presetConfiguration options
To do
  • Move all newly added issues here
  • Move all newly added pull requests here
  • Move all reopened issues here
  • Move all reopened pull requests here
In progress
  • Move all newly opened pull requests here
  • Move all reopened issues here
  • Move all reopened pull requests here
  • Move all pull requests that meet the base branch's minimum number of required reviews here
  • Move all pull requests that no longer meet the base branch's minimum number of required reviews here
Done
  • Move all closed issues here
  • Move all merged pull requests here
  • Move all closed, unmerged pull requests here

Project progress tracking

You can track the progress on your project (classic). Cards in the "To do", "In progress", or "Done" columns count toward the overall project progress. If progress tracking is enabled, a progress bar appears above the project (classic), on the project listing page, in the issue sidebar, and in references to the project on other projects (classic).

For more information, see "Tracking progress on your project (classic)."

Further reading