#gitg — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gitg, aggregated by home.social.
-
I love raccoons!… in a professional way.
https://gitlab.gnome.org/GNOME/gitg/-/issues/519 -
A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:
-
@delighted Well, yes.. that's the ShinyHunters/ScatteredSpider collaboration, but now they have the Salesloft Drift approach, which Google Threat Intelligence Group had tracked as UNC 6395. It looks like GITG just updated the scope of the attack today to any and all authentication tokens stored in or connected to the Drift platform
#SalesloftDrift #Salesforce #GITG #vulnerability #OAuth #Tokens #databreach
-
Scattered Spider Launching Ransomware on Hijacked VMware Systems, Google https://hackread.com/scattered-spider-ransomware-hijack-vmware-systems-google/ #ScatteredSpider #Cybersecurity #Vulnerability #CyberAttacks #CyberAttack #CyberCrime #Scattered #Security #0ktapus #Harrods #vSphere #Google #VMware #Coop #GITG #MS
-
Scattered Spider Launching Ransomware on Hijacked VMware Systems, Google – Source:hackread.com https://ciso2ciso.com/scattered-spider-launching-ransomware-on-hijacked-vmware-systems-google-sourcehackread-com/ #1CyberSecurityNewsPost #CyberSecurityNews #ScatteredSpider #cybersecurity #Vulnerability #CyberAttacks #CyberAttack #CyberCrime #Scattered #Hackread #security #0ktapus #Harrods #vSphere #Google #VMware #Coop #GITG #MS
-
@partizan We need contributors—patch writers and code reviewers—to help with #gitg. Still waiting for someone to step forward to begin a GTK4 port: https://gitlab.gnome.org/GNOME/gitg/-/issues/345#note_1932514
@tbernard -
Can I get a @vala_lang FLOSS hacker interested in this fine newcomers-difficulty-level UX issue to solve in #gitg?
I tried starting to fix it myself a year ago and couldn't figure out how to get past my initial attempt to check the horizontal vs vertical orientation of the layout. I could try again (if I'm desperate enough), but would need a pair programming session with a #Vala enthusiast… or such an enthusiast could probably solve it by themselves in half an hour: https://gitlab.gnome.org/GNOME/gitg/-/issues/424#note_2008428
-
A free 2x performance speedup has now landed in #gitg nightly for every time you click a branch (or any type of ref) in the sidebar :blobaww:
https://gitlab.gnome.org/GNOME/gitg/-/issues/470
Thanks to @GeopJr for creating the fix, and to @albfan for reviewing & merging it!
-
Hide your electric shaver, the #gitg 'stash is coming :blobpeek:
https://gitlab.gnome.org/GNOME/gitg/-/merge_requests/265 -
Huh! Turns out #gitg has no problem fetching other people's anonymous HTTPS repositories, but it chokes on SSH git repositories backed by some SSH keys. Bug report, up for grabs: https://gitlab.gnome.org/GNOME/gitg/-/issues/481
-
Make your #gitg diffs view light-vs-dark aware with this One Weird Trick™ from DJ @GeopJr :blobwizard:
https://gitlab.gnome.org/GNOME/gitg/-/merge_requests/247 -
Another big performance improvement opportunity in #gitg, for those with extremely large changesets who want to commit "the whole file, without looking at the diff", or when viewing an existing commit with a ridiculously large diff, would be to not render large diffs by default, because we'd be hitting limits of what the current source/text view can do, I think?
This might be easy enough for a newcomer to implement! -
Low-hanging fruit performance improvement opportunity in #Gitg for any newcomer (or experienced) #Vala developer: don't reload the view twice when clicking a branch in the sidebar :blobpats: https://gitlab.gnome.org/GNOME/gitg/-/issues/470
The current situation certainly is wasteful, introduces flickering, and doubles the amount of time needed to display something (think of huge #git repositories like Mesa or the Linux kernel, where display performance would be a concern…). I pre-investigated the bug for y'all.
-
I'm sure there are developers on #Linux and #MacOS who would like to use a convenient (and entirely FLOSS) #git desktop GUI to accompany their commandline usage, selectively stage commits, and to generally avoid getting lost in branches and remotes.
Can I convince anyone to help investigate and fix this strange timing bug with the "Commit" button in #gitg? I bet it would turn out to be something silly. https://gitlab.gnome.org/GNOME/gitg/-/issues/421#note_2026990
-
I spent some time assessing all the old, stale branches in #GNOMECalendar's main #git repository, and deleting any branches that were already merged or "so obsolete they'd never get merged" (we're talking 9-years-old branches there).
If you do `git remote update --prune`, 23 stale branches get pruned out as a result, and you get a much clearer view in #gitg ☺️
#GNOME contributors who had forked the Calendar repo a long time ago: don't forget to prune those branches from your fork on gitlab! 😉
-
@konstantin
I don't even use it for writing code (except very occasionally), but I already find #GNOMEBuilder 100% worth using just for building, testing & debugging any project and any branch without having to go through the hassle of having a zillion terminal tabs open to build myself and launch GDB, etc. It has definitely streamlined my workflow as a project manager and QA monkey.Now if we could get a handful more features in #gitg and optimize its performance, we'd have a perfect combo.
-
My latest crackpot idea of the day: what if #gitg could show split-coloured "bubble" labels to combine matching remote vs local branch names in the #git history view and save massive amounts of horizontal space? :blobnom: https://gitlab.gnome.org/GNOME/gitg/-/issues/450
-
I really wish I had a quick and easy way to split #git commits into multiple commits, without having to do interactive rebase surgery by hand with a bunch of steps in the terminal.
It just occurred to me today that this would be a killer feature to have in #GNOME's #gitg app, so here goes a ponies-on-rainbows feature request: https://gitlab.gnome.org/GNOME/gitg/-/issues/448
-
I came up with a #UX refinement idea to solve a bunch of problems in #gitg's layout for author avatar & committer details: use real hyperlinks and combine the timestamps with their #git author/committer, which lets us reduce the number of rows from 4 to 2. Below is a proof of concept I have simulated using the GTK Inspector.
It'd be just some extra logic & markup, probably easy for a #GNOME newcomer to implement; a merge request would be welcomed. https://gitlab.gnome.org/GNOME/gitg/-/issues/440 -
- git cheat sheet von github: https://education.github.com/git-cheat-sheet-education.pdf
- git Buch: http://git-scm.com/book
Ich benutze git meistens auf der Linux-Kommandozeile, um (grafischen) Überblick über Branches zu bekommen verwende ich meistens GitG
Weitere Links (teilweise sogar noch aktuell 😉) und Befehle sammle ich auf meiner eigenen Seite: https://www.unixwitch.de/de/sysadmin/tools/git
-
#gitg is a #Git repository viewer.
gitg opens Git repositories and lists commits, branches, tags, and users. gitg displays commit messages, users involved in a commit, file diffs, all files in a repository, etc. Beyond viewing a repository gitg can also help create commits by managing (un)staged and untracked files and finally committing. gitg can also manage branches, create patches, and more.
Website 🔗️: https://wiki.gnome.org/Apps/Gitg
apt 📦️: gitg
