Hi guys, recently I have realized that the version number in one of my packages does not match with the version in the bioconductor repository ( https://github.com/Genentech/midasHLA/issues/27). The reason is that, while I have been doing no changes past the last few releases a version bump was happening on each Bioconductor RELEASE. Does anyone use some automated way to synchronise between the repositories? GitHub Actions would be an ideal solution. Cheers Maciek
[Bioc-devel] Diverging version numbering on Bioconductor RELEASE
4 messages · migdal migdal, Neumann, Steffen, Mike Smith
4 days later
Hi, so far I am doing this manually, I have my github as remote origin, and the bioc git as upstream, and indeed after the releases I pull from upstream the changed version number and push it to my origin on github. Yours, Steffen
On Sat, 2023-11-11 at 09:35 +0100, migdal migdal wrote:
Hi guys, recently I have realized that the version number in one of my packages does not match with the version in the bioconductor repository ( https://github.com/Genentech/midasHLA/issues/27 ). The reason is that, while I have been doing no changes past the last few releases a version bump was happening on each Bioconductor RELEASE. Does anyone use some automated way to synchronise between the repositories? GitHub Actions would be an ideal solution. Cheers Maciek [[alternative HTML version deleted]]
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
-- Upcoming events: * 2nd ELIXIR-DE Hackathon, 11-15 December 2023 in Bielefeld https://www.denbi.de/de-nbi-events/1547-biohackathon-germany-2 --- IPB Halle Computational Plant Biochemistry (CPB) Dr. Steffen Neumann http://www.ipb-halle.de/ Weinberg 3 Tel. +49 (0) 345 5582 - 1470 06120 Halle +49 (0) 345 5582 - 0 sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
Awesome, thanks for the response! I think it should be possible to put what you are doing manually into GithubActions script, but I am not sure how to do that.
On Wed, Nov 15, 2023, 12:12 Neumann, Steffen <sneumann at ipb-halle.de> wrote:
Hi, so far I am doing this manually, I have my github as remote origin, and the bioc git as upstream, and indeed after the releases I pull from upstream the changed version number and push it to my origin on github. Yours, Steffen On Sat, 2023-11-11 at 09:35 +0100, migdal migdal wrote:
Hi guys, recently I have realized that the version number in one of my packages does not match with the version in the bioconductor repository ( https://github.com/Genentech/midasHLA/issues/27 ). The reason is that, while I have been doing no changes past the last few releases a version bump was happening on each Bioconductor RELEASE. Does anyone use some automated way to synchronise between the repositories? GitHub Actions would be an ideal solution. Cheers Maciek [[alternative HTML version deleted]]
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
-- Upcoming events: * 2nd ELIXIR-DE Hackathon, 11-15 December 2023 in Bielefeld https://www.denbi.de/de-nbi-events/1547-biohackathon-germany-2 --- IPB Halle Computational Plant Biochemistry (CPB) Dr. Steffen Neumann http://www.ipb-halle.de/ Weinberg 3 Tel. +49 (0) 345 5582 - 1470 06120 Halle +49 (0) 345 5582 - 0 sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
Personally I do as Steffen mentioned, and grab the upstream changes manually. Changes not introduced by me only happen once every 6 months, and I'm involved enough with Bioconductor that I generally know when the release and version bump has occurred, so it's never quite felt like enough work to implement an automatic workflow. I think I'm just as likely to forget to put the changes from GitHub to my local machine, and still end up with a merge conflict at some point. However, I think you should be able to use this action from the marketplace to achieve the automatic syncing without too much work creating the workflow: https://github.com/marketplace/actions/upstream-sync Cheers, Mike
On Wed, 15 Nov 2023 at 12:22, migdal migdal <mcjmigdal at gmail.com> wrote:
Awesome, thanks for the response! I think it should be possible to put what you are doing manually into GithubActions script, but I am not sure how to do that. On Wed, Nov 15, 2023, 12:12 Neumann, Steffen <sneumann at ipb-halle.de> wrote:
Hi, so far I am doing this manually, I have my github as remote origin, and the bioc git as upstream, and indeed after the releases I pull from upstream the changed version number and push it to my origin on github. Yours, Steffen On Sat, 2023-11-11 at 09:35 +0100, migdal migdal wrote:
Hi guys, recently I have realized that the version number in one of my packages does not match with the version in the bioconductor repository ( https://github.com/Genentech/midasHLA/issues/27 ). The reason is that, while I have been doing no changes past the last few releases a version bump was happening on each Bioconductor RELEASE. Does anyone use some automated way to synchronise between the repositories? GitHub Actions would be an ideal solution. Cheers Maciek [[alternative HTML version deleted]]
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
-- Upcoming events: * 2nd ELIXIR-DE Hackathon, 11-15 December 2023 in Bielefeld https://www.denbi.de/de-nbi-events/1547-biohackathon-germany-2 --- IPB Halle Computational Plant Biochemistry (CPB) Dr. Steffen Neumann http://www.ipb-halle.de/ Weinberg 3 Tel. +49 (0) 345 5582 - 1470 06120 Halle +49 (0) 345 5582 - 0 sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
[[alternative HTML version deleted]]
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel