On 3/24/2016 2:05 PM, William Marshall wrote:
This is just a guess, but at one point I made a mistake when pushing a
change, and I had to force push to a different state, so the commit tree
looks like this:
a --> b --> c --> e --> f --> g (master)
\-- > d
Where there's one offshoot where the error was made, and it's possible that
gitpubsub requires the entire commit tree to be a pipeline. I doubt this is
the case, but the website hasn't updated since that error, so it's possible.
Did what happened affect the asf-site branch? I think gitpubsub only
looks at that branch.
Kathey
