Thanks again Steffen and Mike for sharing, recently I found some free time
and ended up implementing your suggestions as a GitHub Action.
Maybe this could be of interest to you
https://github.com/Genentech/midasHLA/issues/27#issuecomment-1855795946
Cheers Maciek
On Thu, 16 Nov 2023 at 11:08, Mike
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 i
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 wrote:
> Hi,
>
> so far I am doing this manually, I have my github as remote origin,
> and
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
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
ha
