Thanks for follow-up on this, it should be helpful. > The git revert command was used to create a revert commit. However, the > created commit deleted the entire repository.
Do you have an idea what was a command and how it could deleted the entire repository? I’m asking about this to find a potential solution how we may protect ourself against this in the future. — Alexey > On 16 May 2023, at 21:39, Jack McCluskey via dev <dev@beam.apache.org> wrote: > > Hey everyone, > > Now that 2.47.0 is out, I've got a short write-up on how the repository was > very briefly deleted back when I was cutting the release branch at > https://s.apache.org/beam-repo-deletion-postmortem. This includes the rough > order of operations, the recovery, and then the action items that came from > the experience. It's a very good sign that between Danny McCormick and myself > we were able to knock out two of the three core action items pretty soon > after we got history restored in the repository. As we continue to improve > and simplify the release process we'll hopefully find fewer and fewer avenues > for big issues to pop up. > > Thanks, > > Jack McCluskey > > -- > > > > Jack McCluskey > SWE - DataPLS PLAT/ Dataflow ML > RDU > jrmcclus...@google.com <mailto:jrmcclus...@google.com> > >
