Skip to content

Conversation

@aughr
Copy link
Contributor

@aughr aughr commented Feb 8, 2016

Because dependencies are "transitive" in the global context because they're depended on by a project, we need to ensure that anything a project directly depends on is not excluded from the list of forces.

@aughr aughr force-pushed the fix_updating_global_locks branch 2 times, most recently from 3eac7b2 to 7e7741e Compare February 9, 2016 19:38
@aughr
Copy link
Contributor Author

aughr commented Feb 9, 2016

Updated to scope the change in behavior to global locks only.

@aughr
Copy link
Contributor Author

aughr commented Feb 11, 2016

@quidryan Does this look reasonable? Sorry to explicitly tag you, but you did touch this repo a couple of days ago 😅

@aughr
Copy link
Contributor Author

aughr commented Feb 28, 2016

@rspieldenner @nadavc Does this look OK to you?

Because dependencies are "transitive" in the global context, we need to ensure
that anything a project directly depends on is not excluded from the list of
forces.
@aughr aughr force-pushed the fix_updating_global_locks branch from 7e7741e to 2b37699 Compare May 14, 2016 14:34
@aughr
Copy link
Contributor Author

aughr commented May 14, 2016

@DanielThomas Rebased on master, all green again.

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.

1 participant