-
## Description
Use git history to create a sequence of maps for each commit or at least each time period and allow replaying the whole history as an animation.
## Steps
- When checking out, d…
-
When you commit a change, there is an extra newline between the commit subject and the description, which prevents the information in the git log change history from being displayed on a single line.
-
- *Related to https://github.com/godotengine/godot-proposals/issues/3637,
https://github.com/godotengine/godot-proposals/issues/10311 and
https://github.com/godotengine/godot-proposals/issues/10323.…
-
lib/git_wayback_machine/navigator.rb:44:in 'tput cols'
and
lib/git_wayback_machine/history.rb:14:in 'tput cols'
-
Type: Bug
I work on an extremely large monorepo repository that has about 1M refs, hundreds of thousands of files + directories, 1M+ commits, and takes about 20-40GB on disk depending on the size o…
-
### Issues Policy acknowledgement
- [X] I have read and agree to submit bug reports in accordance with the [issues policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md)
### Where…
-
```
Hi,
After updating a manifest project revision, switching from a previous tag
(v1.12.1) to a newer tag (v1.12.2) on the same branch, repo sync makes git
merge (by recursive method) the newer ta…
-
```
Hi,
After updating a manifest project revision, switching from a previous tag
(v1.12.1) to a newer tag (v1.12.2) on the same branch, repo sync makes git
merge (by recursive method) the newer ta…
-
```
Hi,
After updating a manifest project revision, switching from a previous tag
(v1.12.1) to a newer tag (v1.12.2) on the same branch, repo sync makes git
merge (by recursive method) the newer ta…
-
```
Hi,
After updating a manifest project revision, switching from a previous tag
(v1.12.1) to a newer tag (v1.12.2) on the same branch, repo sync makes git
merge (by recursive method) the newer ta…