Skip to content
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

Separate Build and Deploy Workflows #76

Open
threeal opened this issue May 31, 2024 · 0 comments · May be fixed by #77
Open

Separate Build and Deploy Workflows #76

threeal opened this issue May 31, 2024 · 0 comments · May be fixed by #77
Assignees
@threeal
Labels
ci
Milestone
Future Support

Comments

@threeal
Copy link
Member

threeal commented May 31, 2024

This issue suggests separating the CI workflow into build and deploy workflows. This change is proposed because both workflows have separate triggers. While the build workflow is triggered by pull request events and push events to the main branch, the deploy workflow should only be triggered by push events to the main branch.
@threeal threeal added the ci label May 31, 2024
@threeal threeal added this to the Future Support milestone May 31, 2024
@threeal threeal self-assigned this May 31, 2024
@threeal threeal transferred this issue from b201lab/template-buku-kp-its May 31, 2024
@threeal threeal linked a pull request May 31, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@threeal threeal

Labels
ci
Projects
None yet
Milestone
Future Support
Development

Successfully merging a pull request may close this issue.

Separate Build and Deploy Workflows b201lab/template-proposal-ta-its
1 participant
@threeal