Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Option to preserve commit logs

See original GitHub issue

gitmask squashes all commits into one commit with the message “anonymous commit” by ghost. Though it removes identifications completely, it also loses much information in the change. Commit messages are often important in development.

It would be nice if there’s an option to preserve commit logs and replaces the committer and the author with ghost to remove identifications:

  • Maintainers can get the outline of the request from commit messages.
  • The pull request can be more descriptive by splitting commits in appropriate logical units.

I believe it can be done by running this command in the branch created from the bundle instead of merging that branch into the target branch and squashing commits:

git rebase -f  ${destBranchName} -x "git commit --amend --reset-author"

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

AnalogJcommented, Jun 7, 2020

@ikedam @j-rewerts I just released a new version of Gitmask that acts as a true git remote.

It doesn’t yet support preserving git commit messages, but I’ll be adding support for that in the near future.

ikedamcommented, Apr 6, 2019

@j-rewerts Unfortunately, not yet. I’m a newbie to nodejs and serverless framework and needs much effort to develop this.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How (and why!) to keep your Git commit history clean - GitLab
Git commit history is very easy to mess up, here's how you can fix it!
Read more >
How to manage your Git history: Tips for keeping your commits ...
Your Git commit history should be clear and descriptive – it should ... Save and exit, and the commit to “squash” will be...
Read more >
7.6 Git Tools - Rewriting History
Removing a File from Every Commit ... The --tree-filter option runs the specified command after each checkout of the project and then recommits...
Read more >
Git Squash: How to Condense Your Commit History - CloudBees
The first option (merge) is very simple to perform. ... Keep in mind that you need at least one commit to be picked...
Read more >
Keep commits history after a 'git merge' - Stack Overflow
The last one before branching... while I would like to obtain something like: **Master** commit 09b2unfas9d781n2e Add feature setting commit 8uj8masd89jas898a ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found