chore(ci): ampliar triggers de pipeline hacia rama main - #79
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
chore/ci-trigger-on-main
Descripción
Este cambio actualiza el flujo de trabajo de GitHub Actions (
tests.yml) para incluir la ramamainen los eventos desencadenantes (triggers) depushypull_request. Esto garantiza que cualquier parche urgente (hotfix) o integración hacia el entorno de producción sea validado obligatoriamente por la suite de pruebas, extendiendo la cobertura de Integración Continua que ya opera sobredevelop.Detalles técnicos que integramos:
chore): Se modificaron las directivas deon:en.github/workflows/tests.ymlpara observar tanto amaincomo adevelop.Tipo de cambio
Cómo probar
develop, comprobar en la pestaña Actions de GitHub que el flujo de pruebas se dispara y finaliza con normalidad.main, verificar en GitHub Actions que el pipeline es detonado automáticamente.Checklist