Closed nickvergessen closed 9 years ago
Or better: Just maintain the tests in this repo and load smashbox as an dependency (maybe as a true fork where PRs are started from and the package manager can fetch patched versions from) ;)
Then there is no way to "accidentially" diverge again.
Anyway: Many thanks for the initiative :+1:
@nickvergessen: this sounds entirely reasonable. If this is implemented as you suggest then I will be able to automatically merge all pull requests that are in your part of the project (oc-tests and oc-util). Of course on your side you need to decide what you want to have merged in the upstream smashbox project (and possibly make sure that pull requests are already peer-reviewed or done by a designated person). For changes which are in common I will handle the pull requests with the review on my side. Do you need any special setup from my side that would make it easier for you pull the common changes in the opposite direction i.e. to pull changes in the common smashbox core from the upstream back to your repository (e.g. some tagging or such)?
@jospoortvliet the collection of upstream PRs is in https://github.com/owncloud/smashbox/issues/68
@nickvergessen thanks
Completed
rocking!
Suggested idea
This allows to have a clean cernbox..owncloud/smashbox comparison and to only have new files in owncloud/smashbox..cernbox comparison, so we can cleanly update our copy with cernbox changes all the time and can easily bring our changes upstream.
Fix #113 Fix #68