Howard,
each commits trigger a travis build, and the deploy section of travis
builds the doc and push it if the html has changed
(the pdf contains timestamps, that's why we only focus on the html).
bottom line, the doc will be updated to gh-pages only if it has to.
If the gh-pages repo is updated at each commit and for no reason (e.g.
the doc virtually did not change), then this is
a bug and I will be happy to investigate it.
fwiw, I manually double checked the last commits, and to me, the changes
in the doc were legit.
Cheers,
Gilles
On 10/18/2018 6:57 AM, Ralph H Castain wrote:
Tell the “certain individual” to get over it :-)
We’ve discussed this several times and it isn’t a simple fix. What we want is
to regenerate when something actually changes in the generated files, but we
don’t have a good way of doing it.
I’m sure we would be happy to see a PR from that “certain individual” :-)
Ralph
On Oct 17, 2018, at 2:50 PM, Howard Pritchard <hpprit...@gmail.com> wrote:
Hi Folks,
A certain individual is complaining about the fact that MTT repo currently
is set to have github pages updates following every commit.
I suspect fixing this requires intervention by someone with admin rights on the
repo.
Could we have this feature disabled?
Howard
_______________________________________________
mtt-devel mailing list
mtt-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/mtt-devel
_______________________________________________
mtt-devel mailing list
mtt-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/mtt-devel
_______________________________________________
mtt-devel mailing list
mtt-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/mtt-devel
