[Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it

[Bhagwat, Aditya]

Thankyou Lori,

Is there a way to get a visual overview of recent commits at https://git.bioconductor.org/packages/multicrispr? (as in e.g. github)
Asking because I cannot see recent commits (pushed to upstream successfully yesterday) reflected in build reports<https://bioconductor.org/checkResults/3.12/bioc-LATEST/> or landing page<https://bioconductor.org/packages/devel/bioc/html/multicrispr.html>.
A related question: the CI/CD feature during package submission (master branch push to github triggers build attempt on the BioC servers) was actually very useful, but I can understand that you don't provide this for accepted packages to keep the load on your servers manageable.
What CI/CD setup would you recommend (from the perspective of being maximally relevant for BioC).

Travis?

Thank you for helping!

Aditya

________________________________
From: Shepherd, Lori [Lori.Shepherd using RoswellPark.org]
Sent: Thursday, June 11, 2020 6:18 PM
To: Bhagwat, Aditya; bioc-devel using r-project.org
Subject: Re: [Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it
Newly accepted packages are added into devel only.  They will be a release branch as soon as the next scheduled Bioconductor release occurs.


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 using r-project.org> on behalf of Bhagwat, Aditya <Aditya.Bhagwat using mpi-bn.mpg.de>
Sent: Thursday, June 11, 2020 12:15 PM
To: bioc-devel using r-project.org <bioc-devel using r-project.org>
Subject: [Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it

Dear Bioc Core,

Thank you for accepting multicrispr on BioC<https://secure-web.cisco.com/1Y5aHfpLYwxVOA6Cj3bxEVuenqe6D8K2mYcqfAmwz6Fi6eyzj9ZL85VY2H0PZrFkpkFbO_w5JIWkUIDUjYSFPRsOWFmm_pDVgAJBRmO1uCb9LgJF5mh_FUnj2zUAPVJbk9HPy9BzwWn8pHCQOyHp9T_xfBrl1tFAkt7ZrYGptTyl0u1HYKnjYTmc-l5OjWQoyG3bIOTfYV1lc_cNItl7XwfDdyx4NkyoksEKEZfvA_2PlrkF8te0_49BJxVw47JVUK1Tjj-F-nuVxx2gAF3nDoPiQl1f5bOcc1zKgTYrgh1x2so6QfUHbqu_M7rEFHBQ9OFgeC30W0bOLRd4YEfu5XA/https%3A%2F%2Fgithub.com%2FBioconductor%2FContributions%2Fissues%2F1486>.
I was going through the instructions on how to sync existing repositories<https://secure-web.cisco.com/1Xe9o5uhiFHsFKbmSBGQuqpBQbV-hql0tIGwW7TBNOQyRT67-xND5I-TSMoVXC2pXrgYxNb-5-sPbt5rOOjgawuDHJv7Y7yJFhVBV51tIj9xSy4Nk-GlEPEtV_1RG79MZbJ5d7LZ82dFp-BZmzPwrjKRAib7x8vphKaRW4qc_q6EIPMOrs282w4JaJxxRd-Jsxi6X_gw41rihMwaTa84WG62bi5im6SkX3hoyYq6qwitZdOiUeNN9FYJHB_VREnXcM16haB2xWae5BwiJJdtuP3Y1T-wW9L0HnO14_bhkOd794PH_lDa0cdICiv2NVJVoaSyYZK93SX5T2wpON1FgO_xhi1D5Z45H163FH75DerE/https%3A%2F%2Fbioconductor.org%2Fdevelopers%2Fhow-to%2Fgit%2Fsync-existing-repositories%2F>.
All instructions up to point 9 work.

Point 10, however fails, when creating the release branch:
$ git checkout -b RELEASE_3_11 upstream/RELEASE_3_11
fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created  from it

I wonder what I am doing wrong (seems like it should be something trivial, but I am not seeing it).

Thank you for helping!

Aditya

        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel using r-project.org mailing list
https://secure-web.cisco.com/1dD24Fmu9gjmLPt6fORbREp3nCtIbsBT2Cqq9kX7NWPdnENsspbw0obk03UOZoUcHCDqDJWOZ5LqGeBEON5GsAOUcxgLaOIPiHdXbUkUYRI0JJpGgw9gxTbtdNb5tOM-Tcn6oSrOEmurcRssmw-W7BYV3C5hGKbLQi-Ykb7JeZLS-9VgZSsSCiVcRcC12WqKjR0OmBY6UK1bpRAs--1MCuX1a-WnFzbBEIcdBgOf2IDH6hYDxiFUmniKrXYc52F2MYBhX1qSx1zfJDqxP1bPI1d_4A9MTbwsAuGI9764_XDo3xrBlhnd75yY6a0PaYCvwifkIOcQ2KhxLc0TWUamlFg/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.

	[[alternative HTML version deleted]]