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

[CI] Ignore running pynwb test when merging to dev #207

Merged
merged 1 commit into from
Nov 19, 2019
Merged

Conversation

rly
Copy link
Contributor

@rly rly commented Nov 19, 2019

When PRs are merged to dev, all CI runs again, including the "pynwb-dev-python37" job. This pynwb test job only needs to run on PRs and not on merge. This PR tries to restrict that job running to only PRs but it can only be tested by merging this PR.

@rly rly changed the title [CI] Ignore running pynwb test on non-PR dev [CI] Ignore running pynwb test when merging to dev Nov 19, 2019
@codecov
Copy link

codecov bot commented Nov 19, 2019

Codecov Report

Merging #207 into dev will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##              dev     #207   +/-   ##
=======================================
  Coverage   70.27%   70.27%           
=======================================
  Files          30       30           
  Lines        5944     5944           
  Branches     1395     1395           
=======================================
  Hits         4177     4177           
  Misses       1329     1329           
  Partials      438      438

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c93d595...7ae0d9c. Read the comment docs.

@rly rly merged commit 9ae17f7 into dev Nov 19, 2019
@rly rly deleted the test_circle_pynwb branch November 19, 2019 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants