Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reset project history #13

Open
sugan-reden opened this issue Jan 15, 2025 · 2 comments
Open

Reset project history #13

sugan-reden opened this issue Jan 15, 2025 · 2 comments

Comments

@sugan-reden
Copy link
Contributor

sugan-reden commented Jan 15, 2025

Related to #11

I think I found it! I think I found how to reset the history so that only contributors from the date you started this project are included.

I'm at work currently and can't test it for myself right now, but check this out Git Docs - git-clone --depth.
You can also see --shallow-since=<date> right below which might also be interesting.

We would probably have to git clone --depth 1 quartz and then rebase the project on that.

@sidney-eliot
Copy link
Owner

sidney-eliot commented Jan 15, 2025

I already had a command ready but didn't yet end up executing it as we were talking about other frameworks, in which case it wouldn't have been necessary. Also in addition to that I wanted to still get the newest quartz update before doing it as getting the update would have likely brought it back.

I'm on my phone right now, but basically the command revolved around deleting every name from history that wasn't on a whitelist (sidney-eliot, sugan-reden). Or alternatively, maybe even better, rename every contributor that isn't on the whitelist to "quartz-framework".

To make sure this works properly, I should probably also test this on a fork first. One also has to watch out to get the contributors name correct (which should be the GitHub username, assuming the credentials were set up properly in the forking software like GitHub Desktop or VS Code. But with a git command, one can also print out these names to double-check)

@sidney-eliot
Copy link
Owner

You can also see --shallow-since= right below which might also be interesting.

We would probably have to git clone --depth 1 quartz and then rebase the project on that.

I don't think time would work as old stuff of mine would be deleted from history.

As for the depth argument, it says "specified number of commits" in the doc. How exactly does one specify the commits one wants to keep, without too much effort?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants