search

heroku / cli

Heroku CLI
https://devcenter.heroku.com/articles/heroku-cli
ISC License
852 stars 218 forks source link

Avoid run tests on branch `gh-pages` in Heroku #2005

Open jefer94 opened 2 years ago

jefer94 commented 2 years ago

The gh-pages is managed by MkDocs, I not want every time MkDocs is deployed with Github Actions with the command mkdocs gh-deploy --force, because that branch never ever would contains tests, that cause the CI in Heroku fail each time this branch is updated, but that is a bad approach and ends by waste the resources and money of Heroku and me

sbosio commented 2 weeks ago

Hi @jefer94, can you explain a little bit more in detail what you consider a bad approach.

Am I understanding correctly that you don't want to trigger a CI run when you merge changes that only involve documentation updates generated by mkdocs?

It isn't clear for me if this is specifically a Heroku CLI issue to be reported on this project. I'm not understanding how this relates to the Heroku CLI tool.

We will wait for your answer and review again, or close this report if there's no answer in 30 days.

jefer94 commented 2 weeks ago

Yes it is, I just opened an issue in the first repo more related to the issue, no one says something like "Heroku Test"

jefer94 commented 2 weeks ago

Maybe a manifest or a form would be good to solve this

sbosio commented 2 weeks ago

@jefer94 I still don't see a relationship between your request and the Heroku CLI tool.

If you want to avoid Github Actions to run CI tests on pushes to specific branches or when only certain paths are updated on the repository, then you need to update your GH Actions CI workflow with configurations for that.

Is this what you're looking after: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore?