Merged
Conversation
doutriaux1
added a commit
that referenced
this pull request
Nov 11, 2014
Changes VisTrails URL to Github
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As indicated by my email on Oct 15, I think UV-CDAT should really be using a Github fork of VisTrails to host the VisTrails repository and all the branches. That would allow us developers to use pull requests the way we do for changes on the main UV-CDAT repository (this one, UV-CDAT/uvcdat) and uvcdat-testdata, instead of pushing to vistrails.org and commenting with a branch name.
I am unaware of further discussion on this (didn't see anything on Github or the mailing-list), feel free to comment.
A nightly script updates the fork from vistrails.org right now, we can make it do the contrary when you decide to switch.