If the build report shows the right version, and the page doesn't appear to
be updated (make sure you are checking development page), try a hard
refresh on the page to make sure browser isn't using a cached version (I
think it is Ctrl+shift+F5 on chrome).
Robert
On Sat, Sep 15, 2018, 1:05 PM
Thanks, I used the link you provided to the build report and it seems that the
information did push through.
Best,
John
> On Sep 15, 2018, at 9:38 AM, Martin Morgan wrote:
>
>
>
> On 09/15/2018 12:34 PM, Levi Waldron wrote:
>> John, is your new version number reflected on the devel version
On 09/15/2018 12:34 PM, Levi Waldron wrote:
John, is your new version number reflected on the devel version of the
package landing page and the build report? After you push a new version
number to master, it will propagate the next day after overnight
building/testing.
AFAIK, there are only
John, is your new version number reflected on the devel version of the
package landing page and the build report? After you push a new version
number to master, it will propagate the next day after overnight
building/testing.
AFAIK, there are only a few explanations for why git pushes do not show
Thanks, Robert,
I have updated the files on master GitHub, merged with upstream/master and
pushed to both but I have not seen the website change on Bioconductor in two
days. Am I doing something wrong?
I am following these instructions:
John,
I think that is all pulled directly from the corresponding sections in the
DESCRIPTION file. So you would have to modify the DESCRIPTION, version
bump, and push the changes up.
After the next build, the changes should propagate to the website.
Note that if you only do this on the master
