Set up a GitHub Profile README for an Organization @StatelessCode
Set up a GitHub Profile README for an Organization  @StatelessCode
Uploaded May 2023 | Updated November 2026, 2 hours ago
In this video, we tackle the organization profile README for Stateless Code. We start by assuming (incorrectly) that the structure of an organization profile README is the same as a personal profile README and create a repository with the same name as our org. We create a README for that repository using GitHub's Markdown editor and...

...nothing.

In order for a profile README to show up in an org, you need to have a .github repo for the org (instead of one matching the org name) AND the profile README needs to be located at the path profile/README.md instead of the root README for the .github repo.

We clone the repo onto our machine and add some links to assets. In doing so, we learn that organization profile links can't be relative. We wind up using that statelesscode repo we created at first as the location for the Stateless Code assets, branding, and icons.

Eventually we work out the kinks and get a working README profile associated with our org.

This video covers:
00:00:00 Retrospective introduction after recording the video and noting the pitfalls
00:01:27 Original introduction and example of a GitHub profile README from Atharva Salitri
00:02:43 Create a repo matching the organization name (not the right choice for an organization profile, but we'll still make use of it)
00:04:46 Edit the README on GitHub (and use a draft issue for better markdown editor features)
00:05:59 Review the first draft of the README
00:08:14 Double check links and fix broken or erroneous links
00:13:19 Commit initial changes to the statelesscode.git README, review and discover that organizations need a .github repo
00:15:14 Create a .github.git respository for the organization
00:16:18 Clone both the statelesscode.git and .github.git repos using the command line.
00:18:08 Copy the profile README from the statelesscode repo to the .github repo
00:19:28 Get the Stateless Code branding and assets into the .github repo and replace the placeholder text for Website with a reference to the stateless code logo
00:23:36 Add an image to the top of the README and do a commit on the .github repo
00:25:06 Take a look at GitHub. Not working. The profile README is not in the correct location and the find and replace for the links was not done correctly
00:26:38 Fix malformed markup in README (find and replace error) and force push (twice)
00:30:00 Move the README to the profile directory of the .github repo and change relative links to assets and force push again
00:32:53 Profile README showing up on org profile but relative asset links not working. They need to be absolute links for an org profile
00:34:50 Move the assets to the statelesscode.git repo and push them
00:39:04 Refer to the abosolute links of the assets in the .github repo and remove the assets from the .github repo. Force push again
00:43:27 Validate that everything is working as expected. Reference to assets folder now broken. Fix that and force push one last time

#github #githubprofile #githuborg #orgprofile #readme #orgreadme

See other related StatelessCode videos:
- Create a RubyGem 101: Retro on Version 0.5.0 and Patch Releases youtu.be/FIA8wyaHmnk
- Create a RubyGem 92: Add Contributing Guidelines to the Project youtu.be/IiUWiV2svIU

Resources that we relied upon for this solution:
- Atharva Salitri's GitHub profile github.com/the-amazing-atharva
- Dan Cranney ProfileMe.dev (used for social icons) github.com/danielcranney/profileme-dev

This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
Set up a GitHub Profile README for an OrganizationCodecast: statelesscode.com WordPress 11: Backlog priority, and Footer Link StylingCodecast: statelesscode.com WordPress 16: Move the Footer Widget Back to the FooterMediocre Karaoke - Better Now by Collective SoulThe Path to Rails 8 - Update the GitHub Actions to include Rails 8 EnhancementsExploring My Table Top Role-Playing User PersonaCreate a RubyGem 89: Add Ruby 3.2 to GitHub Actions and Update RSpec to a compatible versionAdd UUID Support and Generate the Devise User ModelAn INCONCEIVABLE RetrospectiveMigrate from SFDX CLI version 7.x to Salesforce CLI version 2.xAdd Code Climate to Project and Allow for Browser Test Driver OptionsInstall Windows Subsystem for Linux 2 (WSL2) and Set Up Remote Development for Visual Studio Code
Stateless Code |

Set up a GitHub Profile README for an Organization

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER