Is there an accepted path and/or filename scheme for Git repository icons?
I noticed that two of the apps I use most frequently (Tower for Mac and Bitbucket.org) have entirely different ways of specifying repository icons: Bitbucket.org requires adding it via the site's UI, while tower asks to add an icon.png
file in the repo root.
Assuming that Git doesn't already support specifying an icon path (assumption based on man git-config
), is anyone aware of a more "standardised" way to monkey-patch repo icons in Git? By more "standardised" I mean something along the lines of the way people use .gitkeep
to commit empty directories whose content shouldn't be committed.
In Git, a head is a ref that points to the tip (latest commit) of a branch. You can view your repository's heads in the path . git/refs/heads/ . In this path you will find one file for each branch, and the content in each file will be the commit ID of the tip (most recent commit) of that branch.
The key difference between Git and GitHub is that Git is an open-source tool developers install locally to manage source code, while GitHub is an online service to which developers who use Git can connect and upload or download resources.
On your repo that you want to add the icons to, create an issue. Drag and drop the icon file into the issue window. Wait for it to download, then it will give you a link. Copy and paste this link into your Readme file at the location you want the icon to appear.
Not that I know of.
If you store the icon in your repo, that won't make a git gui aware of it, unless it is programmed to look for it. Git itself has no special knowledge about that file.
GitHub, for instance, has no special way to illustrate a repo.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With