Re: [PR] Update .asf.yaml to protect current release branches

2022-02-15 Thread Michael Marshall
Are we keeping all of the git history in that transition? If we plan on dropping history, is that something we can do now? Thanks, Michael On Tue, Feb 15, 2022 at 11:19 AM Dave Fisher wrote: > > Before the asf-site branch can deleted the people working on the website need > to finish the transi

Re: [PR] Update .asf.yaml to protect current release branches

2022-02-15 Thread Dave Fisher
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 wrote: > > Now that https://github.

Re: [PR] Update .asf.yaml to protect current release branches

2022-02-15 Thread Michael Marshall
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

[PR] Update .asf.yaml to protect current release branches

2022-02-10 Thread Michael Marshall
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 i