CI not triggered on master branch

unitaryfund / mitiq

Mitiq is an open source toolkit for implementing error mitigation techniques on most current intermediate-scale quantum computers.

https://mitiq.readthedocs.io

GNU General Public License v3.0

363 stars 161 forks source link

CI not triggered on master branch #1080

Closed nathanshammah closed 2 years ago

nathanshammah commented 2 years ago

Pre-Report Checklist

[ ] I am running the latest version of mitiq
[ ] I checked to make sure that this bug has not already been reported

Issue Description

CI has not been triggered on master branch after the latest merge commit, for PR #1077.

How to Reproduce

See https://github.com/unitaryfund/mitiq/commits/master

andreamari commented 2 years ago

It may be due to the [skip ci] codeword that I used in one of the commits of #1077. My intent was to skip the CI tests for that commit but, since [skip ci] appears also in the summary of merge commit, this could have propagated to the final merge too.

Is there a simple way to tirgger tests? Otherwise we can do an empty PR.

nathanshammah commented 2 years ago

@andreamari thanks for the information. I only know how to re-run actions on a job that has already triggered, them, e.g., by clicking the top right button on this page.

nathanshammah commented 2 years ago

Closed by #1082.