[Bioc-devel] Best practice use pkgdown, docker with Bioconductor

Andris Jankevics A@J@nkev|c@ @end|ng |rom bh@m@@c@uk
Tue Apr 6 17:05:06 CEST 2021

Haven't used this, but I think you could use Github Action to merge master branch in the branch for pkgdown whenever changes on master are made.



-----Original Message-----
From: Bioc-devel <bioc-devel-bounces using r-project.org> On Behalf Of Murphy, Alan E
Sent: 06 April 2021 16:24
To: bioc-devel using r-project.org
Subject: [Bioc-devel] Best practice use pkgdown, docker with Bioconductor

Hi all,

I'm working on the development of (EWCE)[https://github.com/NathanSkene/EWCE] and have a question regarding a reviewer note. My package currently uses pkgdown to create a website through the master branch. I also create and push a new docker image from the main branch when the package successfully builds on travis.

My reviewer has asked to remove the related files _pkgdown.yml,Dockerfileanddocker_push from my master branch to avoid any issues with these external configurations and Bioconductor. My reviewer has suggested to put these in another branch. It's not clear to me how best to do this? Ideally, if they are in a separate branch, is there a way to run them once there is an update and successful build on the master branch? If this isn't possible, is there a way to avoid manually duplicating new changes in the master branch in this separate branch and instead, just push the changes from master to this separate branch and trigger pkgdown and docker build that way? Sorry, I realise this last part more so relates to github commands but I was thinking someone else has probably already foudn a way around this issue.

Kind regards,

Alan Murphy
Neurogenomics lab
UK Dementia Research Institute
Imperial College London

	[[alternative HTML version deleted]]

Bioc-devel using r-project.org mailing list

More information about the Bioc-devel mailing list