You didn’t have a build.sh because running build.sh checks out the asf-site branch and leaves you in that state. The asf-site branch only contains the “content” folder. You have to “git checkout master” to get back to the master branch where all the “normal” repo objects are visible. In any case it may be best to start afresh at this point :-)
> On Apr 29, 2016, at 3:12 PM, home4slc <[email protected]> wrote: > > Github user home4slc commented on the pull request: > > > https://github.com/apache/incubator-quarks-website/pull/51#issuecomment-215851894 > > Thanks.. I did not because I did not have a build.sh at that point. > > I’m thinking of blowing everything away and starting fresh. > > Thanks, > > Susan > >> On Apr 29, 2016, at 11:32 AM, Dale LaBossiere <[email protected]> >> wrote: >> >> FYI, I just merged another PR and did a build.sh/push w/o incident. >> The existing build.sh/push didn't complain, so @home4slc >> <https://github.com/home4slc> I'm guessing you didn't yet do build.sh/push >> from #51 <https://github.com/apache/incubator-quarks-website/pull/51>? (and >> your afs-site may be out of sync again) >> Regardless, #51 >> <https://github.com/apache/incubator-quarks-website/pull/51>'s content would >> have been part of my build/push. >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly or view it on GitHub >> <https://github.com/apache/incubator-quarks-website/pull/51#issuecomment-215840757> > > > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at [email protected] or file a JIRA ticket > with INFRA. > ---
