By the way, when I performed ?git remote -v? It is different with yours, I have a ?.git? for upstream origin https://github.com/TheJacksonLaboratory/epihet.git (fetch) origin https://github.com/TheJacksonLaboratory/epihet.git (push) upstream git at git.bioconductor.org:packages/epihet.git (fetch) upstream git at git.bioconductor.org:packages/epihet.git (push) Is it right? Best, Xiaowen From: "Shepherd, Lori" <Lori.Shepherd at RoswellPark.org> Date: Monday, September 21, 2020 at 9:22 AM To: Xiaowen Chen <Xiaowen.Chen at jax.org>, "bioc-devel at r-project.org" <bioc-devel at r-project.org> Subject: [EXTERNAL]Re: Update R package I developed which has been released by bioconductor Bioconductor would not have your package on github. Bioconductor has your repository in a git server. If you already have a clone of your github repository you could follow the instructions here to add the remote to the Bioconductor repository you referenced here: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ so : git clone <Your github repo> cd epihet <follow the instructions on the link above> Make sure you do the git fetch --all git pull upstream master before making any changes!! This will make sure you get the release version bumps the core team performed and that everything is up-to-date with our version of your repository at git.bioconductor.org Once you add the remote upstream if you do git remote -v origin should point to your github upstream should point to Bioconductor It would be something similar to origin https://github.com/<Your<https://github.com/%3cYour> github> .git (fetch) origin https://github.com/<Your<https://github.com/%3cYour> github>.git (push) upstream git at git.bioconductor.org:packages/epihet (fetch) upstream git at git.bioconductor.org:packages/epihet (push) So when you push changes: git push origin master would update YOUR github it is saying git push to the origin which is your github on the master branch To update on Bioconductor git push upstream master it is saying git push changes to the upstream with is the bioconductor remote master branch (devel) Make sure the version number has a version bump! Our version is at 1.5.0 so you would have to bump the z of version x.y.z for it to register on Bioconductor (>= 1.5.1 ) Hope that helps clarify. Lori Shepherd Bioconductor Core Team Roswell Park Comprehensive Cancer Center Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263
From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Xiaowen Chen <Xiaowen.Chen at jax.org>
Sent: Monday, September 21, 2020 8:57 AM
To: bioc-devel at r-project.org <bioc-devel at r-project.org>
Subject: [Bioc-devel] Update R package I developed which has been released by bioconductor
Sent: Monday, September 21, 2020 8:57 AM
To: bioc-devel at r-project.org <bioc-devel at r-project.org>
Subject: [Bioc-devel] Update R package I developed which has been released by bioconductor
Hi, I submit R package called epihet on 2018. It has been accepted and released on Bioconductor. Recently, we received the reviewers? comments about the corresponding paper for epihet, and the reviewer need us to add more parameters for some function in epihet, Could you tell me what I should do step-by-step? Now I know the link 1. http://secure-web.cisco.com/1-EVvVLIafjMbq01E8DqEQNgmvkKvvnjD-0pOAg6fnFQJZO7UJhpm74hsFevQdnOceH8Ueh2BWTT9kb9bsdL13IqIS93SOktOTaRvzl88vZQIjyKpVvpYcasFBguMZ539EF4nnf-yJhgY9ZqzCEecd6Lt5PcT0r6hY6iwYo-kRFbGTZgQvUYbiv4RVLCB0aMNRwNiL_faHaysCM-N9aMnkF0QCtDVuYHDOpwzG0F5eCLtvMhWpKTH29P3I5RfQgzRralE_Wz3O-tYENZrRrhyzlXMEbSEmVj6BtcGZ5p0YdkUaFJ_5NswJT984xe0R4_R/http%3A%2F%2Fbioconductor.org%2Fdevelopers%2Fhow-to%2Fgit%2Fsync-existing-repositories%2F for sync an existing GitHub repository with Bioconductor 2. http://secure-web.cisco.com/1a15GjCpVQyP3eF8WecbERPx8u0-Q3oUVwuRg9flwlizP3Dc6jfSdhF4CRMxd0I4M7S6UAfWCIbVnl67rKj6PsgIKMl5dppsGvqDKq8rf66Cm3qOq2JthrZCWEmdK4xZxV60M5gelNAIlZgVx1Q4HRDN_N4xilgDKIOy5WaMqWYc-57D0HIplyKyzL7xcmCZRnrdmYTfuxIAtS9KhxTHXcp1dfY6CZmW00wMdYPUWfUCkFjSe4_DancgDyMQkmB6EZ4S-PO5qKEdtIAkAEscewyygalAfrQEpiFigAz2iRvFjnDKvTOw5mBH4gvd0eGkb/http%3A%2F%2Fbioconductor.org%2Fdevelopers%2Fhow-to%2Fgit%2Fbug-fix-in-release-and-devel%2F for fix bugs in devel and release but I still not sure which github repository I need to git clone on my local machine, my own github or Bioconductor github, but I did not found my package ?epihet? on Bioconductor github Thank you. Best, Xiaowen --- The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible. [[alternative HTML version deleted]] _______________________________________________ Bioc-devel at r-project.org mailing list https://secure-web.cisco.com/1QwqQZjI0Sbz20Nq-1w66qAgugL1iOh2EVLgNdoGeeQf1Nuzdv2Ou_lMkVxGlJ2mkqCi-z71oTBvFuA3VU2fl5YfMBZye1ywSRTjNwr2gewjPBjz5-vvN5fo3klAPDky0ml6QizcuuBaXHfwiyEwNDk_71_imUofXhsLJN0fbtllSV72ATjHx8t7CPyJSK0V5BV51lYdxHNwjx786mvKEFZ4m3fM9GSEl4eIuyjqj9r9u_tiqssz8O-0YRKEooLwlK0RtTlK2936hBtqq-SWFg00QK5ERpoNZ8tI6g8vJHy5C_2NXBDZ4dU9IK8rFZ9Sw/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-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. --- The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.