Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@sven1103
Copy link
Member

@sven1103 sven1103 commented Apr 9, 2019

The syncing was not very verbose, I changed it, made some refactoring of the code to make it more descriptive (hopefully), and let the script NOT fail, even if errors occured.

The errors will be cought and printed on the travis log though, so we can track issues. But I see no reason to let the travis build fail on a nf-core tools release because of that.

PR checklist

  • This comment contains a description of changes (with reason)
  • If you've fixed a bug or added code that should be tested, add tests!
  • Documentation in docs is updated
  • CHANGELOG.md is updated
  • README.md is updated

Learn more about contributing: https://github.com/nf-core/tools/tree/master/.github/CONTRIBUTING.md

@sven1103 sven1103 requested review from apeltzer, drpatelh and ewels April 9, 2019 09:14
@apeltzer
Copy link
Member

apeltzer commented Apr 9, 2019

Yeah we had a chat about this with @drpatelh and all agreed that its bad to see the entire build fail when actually only sync breaks for some reason and the tools release is actually just fine 👍 Good point @sven1103 ! Will review now!

@sven1103 sven1103 merged commit 16b391b into nf-core:dev Apr 9, 2019
Copy link
Member

@apeltzer apeltzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good to me 👍

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