Skip to content

Instantly share code, notes, and snippets.

@svenfuchs
Last active December 18, 2015 17:49
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save svenfuchs/b83fc36b45bcb0338399 to your computer and use it in GitHub Desktop.
Save svenfuchs/b83fc36b45bcb0338399 to your computer and use it in GitHub Desktop.

Create a new blog post on GitHub

  1. Create a new branch: https://github.com/blog/1377-create-and-delete-branches

Ideally pick a branch name like "sf-add-post-whatever-the-post-title-is", where "sf" are your initials. E.g. "al-add-post-new-teams"

Confirm you're on the new branch by looking at the current URL. The branch name should be part of it.

  1. Navigate to the blog/_posts directory

  2. Add a new file for your post: https://github.com/blog/1327-creating-files-on-github

The filename should follow the naming convention of the existing blog posts: https://github.com/rails-girls-summer-of-code/summer-of-code/tree/gh-pages/blog/_posts. The file extension will determine the format used. Use .md for Markdown.

  1. Add the Jekyll header for the meta data

See https://raw.github.com/RailsGirlsBerlin/summer-of-code/gh-pages/blog/_posts/2013-06-12-hello-world.md for an example. Include the top section including the --- lines and change the attributes where required (probably all of them except the layout attribute).

  1. Add your blog post text
  2. Save the file
  3. Send a pull request: https://help.github.com/articles/creating-a-pull-request

That post explains more than you need. It should work if you just hit the "Pull Request" button, add a title and submit it (target branch and repository names should all default to the right stuff).

@unicornzero
Copy link

@svenfuchs
Copy link
Author

fixed the link, thanks @unicornzero

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