-
Notifications
You must be signed in to change notification settings - Fork 13
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
link to .io page on project page #1
Comments
BTW, here's how we did it on the food inspection project: https://github.com/Chicago/food-inspections-evaluation |
Dear Gene,
Thanks, I will definitely check it out!
Thanks also for the suggestion to provide my link! I’ve added it to the readme.
Cheers,
Shirin
…------------------------------------------------
Dr. Shirin Glander
Department of Genetic Epidemiology
Institute for Human Genetics
University of Münster, Germany
Albert-Schweitzer-Campus 1, D3
Domagkstraße 3
48149 Münster
T +49(0)251-83-56425
F +49(0)251-83-56205
Von: Gene Leynes [mailto:notifications@github.com]
Gesendet: Monday, April 03, 2017 10:38 PM
An: ShirinG/ShirinG.github.io <ShirinG.github.io@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Betreff: Re: [ShirinG/ShirinG.github.io] link to .io page on project page (#1)
BTW, here's how we did it on the food inspection project: https://github.com/Chicago/food-inspections-evaluation
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ASXoJhNorjOu4P-cknPu6-5rOGwdZf6lks5rsVi2gaJpZM4MyD0c>.
|
Glad you like the suggestion, I'm closing the issue 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I suggest that you provide a link to https://shiring.github.io/ShirinG.github.io/ in your https://github.com/ShirinG/ShirinG.github.io/ description.
Unless the user is familiar with constructing the URL they might land on your project page and not find the actual .io page!
The text was updated successfully, but these errors were encountered: