-
Currently the git history seems very cluttered, making it difficult to keep a track of changes.
For example ; [this](https://github.com/rpotter12/whatsapp-play/commit/8bad44f1f0bca11b66b49bf4dff0a824…
-
Oops! I became lazy to remove my notebook outputs before committing, thinking that [GHA would take care of it](https://github.com/spinal-cord-7t/coil-qc-code/actions/runs/11614605882/job/32343166647),…
-
The raw source code is sufficient to comply with the GPL, yet the git history is also extremely valuable. The source doesn't tell us that changes in 5 files were all closely related to solving proble…
-
Hello, I have a error order history when I use the last tag in main tab.
> Here we have main that is a few commits ahead of branches one two and three. For whatever reason, we need to update these …
-
# git rebase & change commits history
-
## Description
## Steps to Reproduce the Problem
1. Given parents `a` and `b`, create a merge commit by doing `jj new a b -m "merge b into a"`.
2. Create a new commit (it can be empty!) a…
-
A while ago infogultch imported the whole of pyspades into git/github I just added stack's work: https://github.com/Ericson2314/pysnip
You should probably then rebase your server modifcations off thi…
-
There seem to be a few binaries in the Git history that force git to clone 100 MB. This should be cleaned up.
-
When working on a feature or bugfix with git, I will commit early and often as I iterate towards the final solution. I rarely want to commit such an array of arbitrary commits. At minimum I will wan…
-
Git's object model has one commit tree history per repository. Commits point to commits and trees. Trees cannot point to commits. (See discussion on alternative here: #4 )
One thing that svn had over…