search

todogroup / gh-issues

A curated set of issues related to GitHub and running corporate scale open source
http://todogroup.org
25 stars 4 forks source link

Provide UI to clean the commit history for a repo #36

Open caabernathy opened 8 years ago

caabernathy commented 8 years ago

A typical flow just before a project launch is we ask project maintainers to clean out history. There should be an easy way to recreate a repo (by an admin) with a completely clean history. What we do today is one of:

  1. Get the code to the state one wants and do a force push to overwrite the current repo. However in this scenario the previous info is available via an API call.
  2. Delete the repo and recreate it. In this case there is no API call leakage. However one typically has to recreate any associated teams and internal tooling.

Perhaps a button in settings under "Delete this repository" named "Clean repository commit history"

lfaraone commented 8 years ago

What's the API call leak?

On Thu, 2 Jun 2016, 15:44 Christine Abernathy, notifications@github.com wrote:

A typical flow just before a project launch is we ask project maintainers to clean out history. There should be an easy way to recreate a repo (by an admin) with a completely clean history. What we do today is one of:

  1. Get the code to the state one wants and do a force push to overwrite the current repo. However in this scenario the previous info is available via an API call.
  2. Delete the repo and recreate it. In this case there is no API call leakage. However one typically has to recreate any associated teams and internal tooling.

Perhaps a button in settings under "Delete this repository" named "Clean repository commit history"

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/todogroup/gh-issues/issues/36, or mute the thread https://github.com/notifications/unsubscribe/AAEewoLUYuKrEfD5h4k_6gAHsE_L3zUHks5qH1y7gaJpZM4ItDXI .

zpao commented 8 years ago

To add to Christina's point (and maybe it clarifies the API leakage, not sure). One of the things that I've experienced is using a repo while it is private and using issues to track the open sourcing progress. Sometimes that will refer to internal infrastructure or code names, but it's nice to be able to have this information associated with a repo while progress is being made. Typically we want that information expunged once open source so as not to leak that information. However issues and pull requests can't be deleted so even if you force push and clear commit history, some things aren't cleared. As a result I've typically gone down path 2 above.

jeffmcaffer commented 5 years ago

Would also like an API.

jeffmcaffer commented 4 years ago

would include some level of cleaning issue and PR history as well.