[Bioc-devel] how to verify upstream git changes
Hi Robert,
On Sep 1, 2017, at 11:16 AM, Robert Castelo <robert.castelo at upf.edu> wrote: hi, i've had a smooth transition from SVN to git for all the software packages i maintain (thanks for the great documentation!!) and i have the following question. i keep a local git repository for each of my software packages, hanging from my github account and this means that i have to push twice every change: git push origin master git push upstream master there maybe different circumstances in which this may not work smoothly including the very stupid one in which i forget to push the changes upstream.
I would suggest a slightly advanced git config setting, if you have trouble remembering to push to both upstream and origin. https://stackoverflow.com/questions/14290113/git-pushing-code-to-two-remotes (Pro-tip)
one may realize that once you see 24hrs later that the build report does not include the updated version. however, i'd like to know if there's some other way to double-check that the changes have been pushed upstream, and of course, something orthogonal to checking whether the command was written.
A good way to check if the push went through will be to just clone the repo in a tmp directory, and check if the latest commit shows. We are going to have a naive UI sometime soon, and that way, you can just log in and see that your commit has been posted. It will most likely be a gitweb interface.
in the past i was subscribed to the RSS feed of the SVN changes, so i could easily check from my browser whether the changes were really committed. this was quite critical for me when working with the svn-git bridge, cherry picking changes, etc.. is there anything analogous to that SVN RSS feed with the current git setup at bioconductor?
Hope this helps for the time being. Best, Nitesh
thanks!! robert.
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.