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.

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

Trigger Actions on update/pixi-lock #1996

Open
visr opened this issue Jan 6, 2025 · 0 comments
Open

Trigger Actions on update/pixi-lock #1996

visr opened this issue Jan 6, 2025 · 0 comments
Labels
CI/CD Continuous Integration/Continuous deployment

Comments

@visr
Copy link
Member

visr commented Jan 6, 2025

I missed #1994 in #1992 since I now see only TeamCity was triggered but not GitHub Actions. Any ideas what goes wrong? We already select the branch name update/pixi-lock:

on:
push:
branches: [main, update/pixi-lock]
paths-ignore: [".teamcity/**"]
tags: ["*"]
pull_request:
paths-ignore: [".teamcity/**"]

@visr visr added the CI/CD Continuous Integration/Continuous deployment label Jan 6, 2025
@github-project-automation github-project-automation bot moved this to To do in Ribasim Jan 6, 2025
@SnippenE SnippenE moved this from To do to Sprint backlog in Ribasim Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Continuous Integration/Continuous deployment
Projects
Status: Sprint backlog
Development

No branches or pull requests

1 participant