New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support custom (per repository) og:image thumbnails. #612

Open
bvaughn opened this Issue Mar 18, 2016 · 52 comments

Comments

Projects
None yet
@bvaughn

bvaughn commented Mar 18, 2016

Edit Please upvote this issue with a 馃憤rather than leave a "+1" comment. GitHub sorts issues by reactions and not by the number of comments.

Github currently sets the twitter:image:src and og:image meta tags for each of my repositories to be that of my main profile picture. This seems like a reasonable default. But it would be useful if there were a way to override this setting on a per-repository basis. (Perhaps a convention that uses a specially-named file in the root of a repository? Or something in the project settings?)

It's a minor issue but it would be nice when I share a link to a new version release on sites like Twitter, Reddit, etc. if the thumbnail was a project logo rather than my profile picture.

I realize that I can sometimes link to my own gh-pages branch and set any meta tags I want but I usually prefer the simplicity of linking directly to the GH repository landing page. Other times it's not even an option, like when linking to a wiki page with upcoming release notes (example).

@edgariscoding

This comment has been minimized.

edgariscoding commented Mar 26, 2016

Great idea

@itaibh

This comment has been minimized.

itaibh commented Mar 31, 2016

Not only this is a great idea, I don't think this is a reasonable default.

@zzgab

This comment has been minimized.

zzgab commented Sep 16, 2016

Any update about this great feature request?

@edgariscoding

This comment has been minimized.

edgariscoding commented Sep 16, 2016

Also wondering if there's been any development on this. I like having a profile photo of myself but it's a bit weird when I share a link to a repository and it shows a huge thumbnail of my face.

@zzgab

This comment has been minimized.

zzgab commented Sep 18, 2016

All I could come up with, is making a gh-pages branch for my project uiwebagent
This gh-pages contains an index.html file in which I declare the meta that I like (useful for FB og, Twitter etc.) but then the body only forces a JS redirect to the GitHub master repository...
So, the link I provide in my Twitter posts for instance, is https://zzgab.github.io/uiwebagent
Not happy with this workaround...

@housseindjirdeh

This comment has been minimized.

housseindjirdeh commented Dec 28, 2016

I think this would be a great idea, and I agree, that is a bit much of a workaround @zzgab

@edgariscoding

This comment has been minimized.

edgariscoding commented Feb 2, 2017

There really should be a place within the repo settings to assign a repo thumbnail just like you can for organization pages or profile pages.

@theiliad

This comment has been minimized.

theiliad commented Mar 6, 2017

Any updates here?

@JustineWin

This comment has been minimized.

JustineWin commented Mar 7, 2017

I guess a custom og: still isn't available. Tried creating a new website this week and put all those og: meta tags but nothing works :D Still hoping github considers this feature :)

@i-h

This comment has been minimized.

i-h commented Aug 6, 2017

Seconding this, posting with a collaborator's (who made the repository) face on Twitter feels kind of rude.

@edgariscoding

This comment has been minimized.

edgariscoding commented Nov 1, 2017

Is there any development on this? Even a simple setting to disable the use of a custom thumbnail altogether would be sufficient in the meantime.

@ghost

This comment has been minimized.

ghost commented Nov 1, 2017

pls gitahubb do dis 4 us

@daattali

This comment has been minimized.

daattali commented Nov 2, 2017

Great idea!

@haideralipunjabi

This comment has been minimized.

haideralipunjabi commented Nov 2, 2017

This should be added ASAP

@chetcuti

This comment has been minimized.

chetcuti commented Nov 2, 2017

Yes please.

@Almenon

This comment has been minimized.

Almenon commented Nov 7, 2017

this would be a very nice feature.

@michaelashore

This comment has been minimized.

michaelashore commented Nov 13, 2017

This feature would be great and I suspect would encourage more sharing of repos across Facebook and Twitter.

@clarkbw

This comment has been minimized.

Collaborator

clarkbw commented Nov 14, 2017

Perhaps a convention that uses a specially-named file in the root of a repository? Or something in the project settings?

@bvaughn So you'd be ok to set a specific repository image? Perhaps it might default to your user image as it does now if not already set.

(this is a mockup, just wanted clarify; no promises)

screen shot 2017-11-13 at 7 52 02 pm

@edgariscoding

This comment has been minimized.

edgariscoding commented Nov 14, 2017

So you'd be ok to set a specific repository image? Perhaps it might default to your user image as it does now if not already set.
(this is a mockup, just wanted clarify; no promises)

@clarkbw I'm not speaking for @bvaughn but yes, that would be amazing.

@bvaughn

This comment has been minimized.

bvaughn commented Nov 14, 2017

Hey @clarkbw! Nice to hear from you. 馃槃

Honestly, I would be okay with almost any way to do this. An option in the project settings area would be great. That seems the most backwards-friendly way of approaching this, and avoids bloating the repo with an unnecessary image file. 馃憤

@spcfran

This comment has been minimized.

spcfran commented Nov 28, 2017

Can I have this for Xmas? Trying to add a link to a repo to my LinkedIn profile for showcase/portfolio purposes and my face is all over it! 馃槄

+1 for the project scoped setting rather than a file in the repo - it's a very 'meta' thing after all

@zzgab

This comment has been minimized.

zzgab commented Nov 29, 2017

@spcfran All in all, despite its tweaky-tricky-hacky aspect, we've got nothing but my workaround here : #612 (comment)
I've been using it successfully all this time, but it's a pain in the back.

@edgariscoding

This comment has been minimized.

edgariscoding commented Nov 29, 2017

@zzgab that鈥檚 a pretty clever workaround. The bad thing is that it only works for the repo owner because other people sharing the repo won鈥檛 care to jump through hoops, they鈥檒l just share the direct link to the repo.

Does anyone know if Github actually confirms when they鈥檙e working on a new feature before it鈥檚 released?

@zzgab

This comment has been minimized.

zzgab commented Nov 29, 2017

@edgariscoding You're right.

@clarkbw

This comment has been minimized.

Collaborator

clarkbw commented Nov 29, 2017

Can this issue be labeled social or something similar? Categorizing these issues really helps with the clutter. kthx!

@valentinchrt

This comment has been minimized.

valentinchrt commented Dec 13, 2017

It would be great @clarkbw, really.
Tell us that this feature will be release soon! 馃巵

@edgariscoding

This comment has been minimized.

edgariscoding commented Dec 13, 2017

@clarkbw, is setting a label on this issue something that @bvaughn can do or were you commenting so that someone with admin rights on the repo can do it?

@clarkbw

This comment has been minimized.

Collaborator

clarkbw commented Dec 13, 2017

commenting so that someone with admin rights on the repo can do it?

It requires admin rights which I don't have and I don't believe @bvaughn has either. I emailed @isaacs about it a while ago but I never heard back 馃槶

@clarkbw

This comment has been minimized.

Collaborator

clarkbw commented Dec 13, 2017

And FYI, I don't have anyone actively working on this right now. I'm hoping to convince the marketing team to pick this up with some other work they are planning for the coming year. We'll see.

@KelvinShadewing

This comment has been minimized.

KelvinShadewing commented Dec 21, 2017

Gah, marketing always gets in the way of useful development. Ironic here, since the target audience is developers. XP I, too, would love to have this feature. It would certainly help repos stand out from one another, especially if someone has a bunch of them in one account.

@shangyilim

This comment has been minimized.

shangyilim commented Jan 1, 2018

+1 on this idea as well. Would love to show some more interesting thumbnail pictures, rather than my profile picture.

@actuallyaswin

This comment has been minimized.

actuallyaswin commented Jan 31, 2018

@KelvinShadewing this is important for developers too! When sharing your Github projects with recruiters or employers, you'll want the metadata to look nice and fancy. Same goes with sharing projects on Facebook or Twitter!

@KelvinShadewing

This comment has been minimized.

KelvinShadewing commented Feb 2, 2018

@actuallyaswin Which is exactly why we need per-repo thumbnails.

@edgariscoding

This comment has been minimized.

edgariscoding commented Feb 2, 2018

Maybe we should go to different developer communities and forums and ask them what they think and to come comment if they agree.

@ahsouza

This comment has been minimized.

ahsouza commented Feb 12, 2018

We need this!
My situation to have this feature is when we add our repositories on LinkedIn media and is boring see all links with same image (user avatar)

@lucasmafra

This comment has been minimized.

lucasmafra commented Mar 16, 2018

This is a really important feature! Any updates on that?

@igalbn

This comment has been minimized.

igalbn commented Mar 18, 2018

During write post on LinkedIn. When attaching the link to repository. LinkedIn show as thumbnail my big and streched photo. Instead prefer, use image of my program.

@izgeri

This comment has been minimized.

izgeri commented Mar 22, 2018

Just popping by to join the chorus and say it would be great if this feature were added! I don't love seeing my face in my tweets about my gh repo - I wish I could set a repo-specific image to use instead!

@clarkbw

This comment has been minimized.

Collaborator

clarkbw commented Mar 22, 2018

Thanks for the feedback here!

Friendly reminder to always 馃憤 the first comment (I don't know if you also did that @izgeri) because I sort these issues by reaction and not by most commented.

@iamciera

This comment has been minimized.

iamciera commented Mar 23, 2018

I also would LOVE to have this feature.

@edgariscoding

This comment has been minimized.

edgariscoding commented Mar 23, 2018

@mikedeshazer

This comment has been minimized.

mikedeshazer commented Jun 7, 2018

PLEASE. To this feature

@rcmaples

This comment has been minimized.

rcmaples commented Jun 17, 2018

I wish we had thumbnails already.. Upvoting for thumbnails!

@jmarshall

This comment has been minimized.

jmarshall commented Jun 18, 2018

Perhaps a convention that uses a specially-named file in the root of a repository? Or something in the project settings?

馃憤 but definitely via something in the project settings. Using a specially-named file in the repository would mean that your image was automatically propagated to other people's newly-created forks, which would often not be desirable.

@edgariscoding

This comment has been minimized.

edgariscoding commented Jun 18, 2018

@jmarshall good point regarding the image being automatically propagated to other people's forks. I think a setting in project settings would be ideal.

@itaibh

This comment has been minimized.

itaibh commented Jun 19, 2018

@jmarshall

This comment has been minimized.

jmarshall commented Jun 19, 2018

@itaibh: There's a number of possibilities as to what different projects might want a thumbnail to represent:

  • A customised personal or institutional avatar. Must not be automatically propagated to other forks, just as today's user or organisation avatar is not.

  • A project logo with a firefox/iceweasel trademark situation. If it's automatically propagated to other forks, the original org will choose not to use this facility.

  • An unencumbered logo representing the project. Propagation to other forks would be acceptable in this case, though make it harder to recognise the canonical source at a glance.

A file in the repo is pretty much all or nothing. A project setting allows for an implementation where (1) on forking, the new forker is asked whether to propagate the source custom avatar 鈥 provided (2) the source fork has not set the do-not-propagate-avatar option. That sort of complexity would be needed to handle all the possibilities I've listed.

@KelvinShadewing

This comment has been minimized.

KelvinShadewing commented Jun 19, 2018

The only way to reliably verify canon is to look at the URL the project is hosted at, so you might as well leave the file in the repo. Though for browsing, you could have the user's icon appear in the lower corner for a quicker identifier. Maybe GitHub could generate a thumbnail with an icon overlay for use in OG tags.

@0biWanKenobi

This comment has been minimized.

0biWanKenobi commented Jul 29, 2018

Please, pretty please do this GitHub team 鉂わ笍

@AnthumChris

This comment has been minimized.

AnthumChris commented Oct 19, 2018

What about specifying images in .gitattributes file similar to how we already configure Linguist using gitattributes? This could offer better scalability as preview image specs change:

images/logo-200x200.png preview-image=twitter-small
images/logo-600x300.png preview-image=twitter-large
images/logo-1200x630.png preview-image=facebook
images/logo-1200x627.png preview-image=linkedin
@edgariscoding

This comment has been minimized.

edgariscoding commented Oct 19, 2018

@nonoesp

This comment has been minimized.

nonoesp commented Nov 26, 2018

Looking forward to using this when it's implemented!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment