Skip to main content

Personalizing your profile

You can share information about yourself with other GitHub users by setting a profile picture and adding a bio to your profile.

Note: Any details you add to your public GitHub profile will be visible to all GitHub users, including in regions where local laws, regulations, or cultural norms may pose risks to expressing your identity. We respect everyone’s decision about whether or not to share information about themselves on their GitHub profile.

Changing your profile picture

Your profile picture helps identify you across GitHub in pull requests, comments, contributions pages, and graphs.

When you sign up for an account, GitHub provides you with a randomly generated "identicon". Your identicon generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.

Note: Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.

If you use Gravatar, and your Gravatar image is associated with the email you use for GitHub, the image will be shown as your GitHub profile picture by default (rather than an identicon). To change your GitHub profile picture, you can either upload a new image to Gravatar, or upload a new image to GitHub and override the Gravatar image.

Setting a profile picture

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.

  2. Under "Profile Picture", select Edit, then click Upload a photo....

    Screenshot of the "Public profile" section of a user account's settings. A button, labeled with a pencil icon and "Edit", is outlined in dark orange.

  3. Select an image, then click Upload.

  4. Crop your picture.

  5. Click Set new profile picture.

Resetting your profile picture to the identicon

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.

  2. Under "Profile Picture", select Edit, then click Remove photo to revert to your identicon.

    If your email address is associated with a Gravatar, you cannot revert to your identicon. Click Revert to Gravatar instead.

    Screenshot of the "Public profile" section of a user account's settings. A button, labeled with a pencil icon and "Edit", is outlined in dark orange.

Changing your profile name

You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "Managing the display of member names in your organization."

Note: If you're a member of an enterprise with managed users, any changes to your profile name must be made through your identity provider instead of GitHub. For more information, see "Types of GitHub accounts."

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
  2. Under "Public profile", in the "Name" field, type the name you want to be displayed on your profile.

Adding a bio to your profile

Add a bio to your profile to share information about yourself with other GitHub users. With the help of @mentions and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.

For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "Managing your profile README."

Note: If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "Showing an overview of your activity on your profile."

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.

  2. Under "Public profile", in the "Bio" field, type the content that you want displayed on your profile. The bio field is limited to 160 characters.

    Tip: When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.

  3. Click Update profile.

Adding pronouns to your profile

Add pronouns to your public user profile to share information about yourself with other GitHub users. Your pronouns will only be visible to users that are signed in to GitHub.

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.

  2. Under Pronouns, add the pronouns that you want displayed on your profile. You may add custom pronouns.

  3. Click Update profile.

Setting your location and time zone

You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:

  • On your GitHub profile page
  • When people hover over your username or avatar on GitHub

Screenshot of the Octocat profile page emphasizing the location, local time, and relative time fields.

When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated. When others view your profile, they will see your location, local time, and the time difference in hours from their own local time.

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
  2. Under "Public profile", in the "Location" field, type the location you want to be displayed on your profile.
  3. Optionally, display the current local time on your profile.
    • Select Display current local time.
    • Select the Time zone dropdown menu, then click your local time zone.
  4. Click Update profile.

You can add up to four links to social accounts on your profile. These are visible to anyone who can view your profile.

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
  2. Under "Social accounts", in a blank "Link to social profile" field, type the full URL of the social account. For example, for the @GitHub Twitter account, type https://twitter.com/github.
  3. Click Update profile.

Adding your ORCID iD to your profile

If you're a researcher with an ORCID iD, you can identify yourself by adding your ORCID iD to your profile.

  1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
  2. Under "ORCID iD", click Connect your ORCID iD.
  3. Follow the steps to sign in to your ORCID account and then return to GitHub.

Setting a status

You can set a status to display information about your current availability on GitHub. Your status will show:

  • On your GitHub profile page
  • When people hover over your username or avatar on GitHub
  • On a team page for a team where you're a team member. For more information, see "About teams."
  • On the organization dashboard in an organization where you're a member. For more information, see "About your organization dashboard."

When you set your status, you can also let people know that you have limited availability on GitHub.

If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "Managing code review settings for your team."

Screenshot of a draft comment. "@octocat" is written in the text field, and "The Octocat (busy)" is suggested.

  1. In the top right corner of GitHub, select your profile photo, then click Set status or, if you already have a status set, click your current status.

    Screenshot of the dropdown menu under @octocat's profile picture. A smiley icon and "Set status" are outlined in dark orange.

  2. In the "What's happening" field, type a status message.

  3. Optionally, to set an emoji status, click , then click an emoji from the list.

  4. Optionally, if you'd like to share that you have limited availability, select "Busy."

  5. Select the Clear status dropdown menu, then click when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.

  6. Select the Visible to dropdown menu, then click who you want your status visible to. If you don't select an organization, your status will be public.

  7. Click Set status.

Displaying badges on your profile

When you participate in certain programs, GitHub automatically displays a badge on your profile.

BadgeProgramDescription
Developer Program MemberIf you're a registered member of the GitHub Developer Program, building an app with the GitHub API, you'll get a Developer Program Member badge on your profile. For more information on the GitHub Developer Program, see GitHub Developer.
ProIf you use GitHub Pro you'll get a PRO badge on your profile. For more information about GitHub Pro, see "GitHub’s plans."
Security Bug Bounty HunterIf you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the GitHub Security program, see GitHub Security.
GitHub Campus ExpertIf you participate in the GitHub Campus Program, you will get a GitHub Campus Expert badge on your profile. For more information about the Campus Experts program, see Campus Experts.
Security advisory creditIf a security advisory you submit to the GitHub Advisory Database is accepted, you'll get a Security advisory credit badge on your profile. For more information about GitHub Security Advisories, see GitHub Security Advisories.

Earning Achievements

Achievements celebrate specific events and actions that happen on GitHub. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access.

To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "Showing your private contributions and achievements on your profile."

Note: This feature is currently in public preview and subject to change.

List of qualifying repositories for Mars 2020 Helicopter Contributor achievement

The Mars 2020 Helicopter Contributor achievement was given to those who had authored a commit for one of the repositories listed below. This event has now ended, and the badge is no longer available. We built the list based on information received from NASA's Jet Propulsion Laboratory.

GitHub RepositoryVersionTag
torvalds/linux3.4v3.4
python/cpython3.9.2v3.9.2
boto/boto31.17.171.17.17
boto/botocore1.20.111.20.11
certifi/python-certifi2020.12.52020.12.05
chardet/chardet4.0.04.0.0
matplotlib/cycler0.10.0v0.10.0
elastic/elasticsearch-py6.8.16.8.1
ianare/exif-py2.3.22.3.2
kjd/idna2.10v2.10
jmespath/jmespath.py0.10.00.10.0
nucleic/kiwi1.3.11.3.1
matplotlib/matplotlib3.3.4v3.3.4
numpy/numpy1.20.1v1.20.1
opencv/opencv-python4.5.1.4848
python-pillow/Pillow8.1.08.1.0
pycurl/pycurl7.43.0.6REL_7_43_0_6
pyparsing/pyparsing2.4.7pyparsing_2.4.7
pyserial/pyserial3.5v3.5
dateutil/dateutil2.8.12.8.1
yaml/pyyaml5.4.15.4.1
psf/requests2.25.1v2.25.1
boto/s3transfer0.3.40.3.4
enthought/scimath4.2.04.2.0
scipy/scipy1.6.1v1.6.1
benjaminp/six1.15.01.15.0
enthought/traits6.2.06.2.0
urllib3/urllib31.26.31.26.3
python-attrs/attrs19.3.019.3.0
CheetahTemplate3/cheetah33.2.43.2.4
pallets/click7.07.0
pallets/flask1.1.11.1.1
flask-restful/flask-restful0.3.70.3.7
pytest-dev/iniconfig1.0.0v1.0.0
pallets/itsdangerous1.1.01.1.0
pallets/jinja2.10.32.10.3
lxml/lxml4.4.1lxml-4.4.1
Python-Markdown/markdown3.1.13.1.1
pallets/markupsafe1.1.11.1.1
pypa/packaging19.219.2
pexpect/pexpect4.7.04.7.0
pytest-dev/pluggy0.13.00.13.0
pexpect/ptyprocess0.6.00.6.0
pytest-dev/py1.8.01.8.0
pyparsing/pyparsing2.4.5pyparsing_2.4.5
pytest-dev/pytest5.3.05.3.0
stub42/pytz2019.3release_2019.3
uiri/toml0.10.00.10.0
pallets/werkzeug0.16.00.16.0
dmnfarrell/tkintertable1.2v1.2
wxWidgets/wxPython-Classic2.9.1.1wxPy-2.9.1.1
nasa/fprime1.3NASA-v1.3
nucleic/cppy1.1.01.1.0
opencv/opencv4.5.14.5.1
curl/curl7.72.0curl-7_72_0
madler/zlib1.2.11v1.2.11
apache/lucene7.7.3releases/lucene-solr/7.7.3
yaml/libyaml0.2.50.2.5
elastic/elasticsearch6.8.1v6.8.1
twbs/bootstrap4.3.1v4.3.1
vuejs/vue2.6.10v2.6.10
carrotsearch/hppc0.7.10.7.1
JodaOrg/joda-time2.10.1v2.10.1
tdunning/t-digest3.2t-digest-3.2
HdrHistogram/HdrHistogram2.1.9HdrHistogram-2.1.9
locationtech/spatial4j0.7spatial4j-0.7
locationtech/jts1.15.0jts-1.15.0
apache/logging-log4j22.11log4j-2.11.0

Further reading