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.

Sign up for GitHub

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

Jump to bottom

Investigate and resolve issues with fork being out of date #6

Open

micahjsmith opened this issue Aug 18, 2020 · 0 comments

Labels

bug enhancement

Contributor

micahjsmith commented Aug 18, 2020 •

edited

Loading

Description

If fork exists, then assemble will not create a new fork, obviously. So the fork may be out of date with the upstream project.

Possible outcome:

fork is cloned
fork specifies ballet version x but project has been updated to use ballet version y
project structure of fork could be different
config file of fork could be different

Possible resolutions

if fork is not created by API call, then fork already exists. try to update fork to upstream before proceeding
catch errors and report them to user

The text was updated successfully, but these errors were encountered:

micahjsmith added bug enhancement labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment