I agree with Marton. Force pushing to a public git repo is likely to be very disruptive going forward, and the only safe approach to deal with the committed secret is to revoke it and add a new commit to remove it. If it's revoked, having it in the git history will do no harm.
+1 to what Maron suggested. On Thu, Mar 25, 2021 at 7:49 AM Elek, Marton <e...@apache.org> wrote: > > > > > 4. Force-pushing invalidates all of our commit ids which are part of > > our development history: the pull requests. All the merge links on the > > reworked PRs now points to invalid commits which are not part of the > master. > > > As far as I see all of our open PRs are also broken and/or conflicted: > > > Like this one: > > https://github.com/apache/ozone/pull/2065 > > It supposed to be a simple dependency change AFAIK. > > > Marton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > For additional commands, e-mail: dev-h...@ozone.apache.org > >
