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

Certain PRs do not trigger the CI workflow and need to be merged manually with branch protections bypassed #1762

Closed
jessebraham opened this issue Jul 5, 2024 · 1 comment · Fixed by #1821
Assignees
Labels
CI Continuous integration/deployment
Milestone

Comments

@jessebraham
Copy link
Member

See:

@jessebraham jessebraham added the CI Continuous integration/deployment label Jul 5, 2024
@tom-borcin tom-borcin added this to the 0.20.0 milestone Jul 15, 2024
@bjoernQ
Copy link
Contributor

bjoernQ commented Jul 16, 2024

I thought about having a dummy_ci.yml workflow which only triggers on CHANGELOG and README but I think that would be very dangerous - i.e. having a failing build and then changing CHANGELOG.md would result is everything being shiny green.

So probably the only safe thing to do it to not path-exclude in ci.yml?

@SergioGasquez SergioGasquez self-assigned this Jul 17, 2024
@SergioGasquez SergioGasquez linked a pull request Jul 17, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous integration/deployment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants