Before the asf-site branch can deleted the people working on the website need to finish the transition of https://github.com/apache/pulsar-site to build the main site and not a staging site.
All the best, Dave > On Feb 15, 2022, at 8:55 AM, Michael Marshall <mmarsh...@apache.org> wrote: > > Now that https://github.com/apache/pulsar/pull/14226 is merged, our > current release branches are correctly protected from force pushes. > > Importantly, the `asf-site` branch is no longer protected. That branch > is responsible for quite a bit of data in our git repo. Anecdotally, > when I tried to clone the apache/pulsar repo yesterday, it took 10 > minutes to clone about 40% of the repo. It'd be great to reduce the > overall size of our git repo. What is the status of the plan to move > that branch or remove some or all of its history? > > Thanks, > Michael > > On Thu, Feb 10, 2022 at 6:00 PM Michael Marshall <mmarsh...@apache.org> wrote: >> >> Hello, >> >> Our current apache/pulsar GitHub repo does not have protections on our >> current release branches. I think we should protect against deletion >> and force pushes, at a minimum. >> >> Here is my PR to update the .asf.yaml to comply with these rules: >> https://github.com/apache/pulsar/pull/14226. There is more detail in >> the PR. Please review, if you're interested. >> >> Thanks, >> Michael
