Hide PR checks for skipped jobs

Hi,

I have a workflow that consists of two jobs, one for building and testing my code and another one to deploy releases to bintray/jcenter.

Since I only want to publish tagged versions, the second job runs only for tags:

jobs:
  ...
  deploy:
    if: startsWith(github.ref, 'refs/tags/')
    ...

But now in every Pull Request the skipped deploy-job is reported as a check with the status “Skipped”, which doesn’t break anything as the check is not required, but is completely unnecessary.

Is there a way to disable the check to be reported for that job? Or to report the workflow run instead of each individual job?

An alternative would be to move the deploy-job into a separate workflow triggered on tags, but this way I would have to duplicate the build/check job if publishing the tagged version shall depend on it.

@christopherfrieler,

It’s a designed behavior that the skipped checks still are listed on the PR. And currently we have any setting option or workaround to disable this behavior.

If your projects really need the feature that disable to show the skipped checks on the PR, I recommend that you can directly report a feature request here. That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions.

Hi @brightran,

thank you for your response and for pointing me to the feedback form. I will report my feature request there.

It’s a designed behavior that the skipped checks still are listed on the PR.

What is the intention behind this? Can you (or someone else from the community) give an example, where this behaviour is desired? I can’t imagine one, but maybe I’m just working against some design idea of Github Actions that I didn’t understand yet.

@christopherfrieler,

What is the intention behind this?

I have created an internal ticket to help you report this question to the appropriate engineering team for further discussion and evaluation. Maybe the engineering team can give a reasonable explanation.

If they have any progress, I will notify you in time, and sometimes the appropriate engineers may directly reply you here.