Posts

Showing posts with the label zperfumes.ph

What Settings Should You Configure After Creating a GitHub Repository

By -

Why Are Post-Creation Settings Important in a GitHub Repository

Once you've created a new GitHub repository for your Jekyll-based blog, especially using the Mediumish theme, you're only halfway done. Most beginners overlook the vital configuration settings that determine whether your blog will render properly, be indexed by search engines, or even deploy at all. Understanding and optimizing your repository settings ensures smooth integration with GitHub Pages, secure access, and faster setup.

What Are the Key Areas You Need to Configure

After the repository is created, the following areas must be reviewed:

  • Repository visibility
  • Branch configuration
  • GitHub Pages source setting
  • Web URL preview
  • Repository metadata
  • Collaborator and access control
  • License and readme verification

How to Set the Correct GitHub Pages Branch and Folder

For Jekyll to work with GitHub Pages, you must set the correct deployment source. This can be configured under the repository’s Settings → Pages tab.

Steps to Set GitHub Pages Source Correctly

  1. Go to your repository
  2. Click Settings
  3. Scroll down to the Pages section
  4. Under Source, choose:
    • Deploy from a branch
    • Select the branch: usually main
    • Folder: select / (root) if your Jekyll files are directly in the root
  5. Click Save

After setting this, GitHub will trigger a build and assign a live site URL (e.g. https://yourusername.github.io/repositoryname/).

What Visibility Setting Should You Use for a Jekyll Blog

By default, new repositories are public, which is required if you’re using GitHub Pages to host your blog without a paid plan. Private repositories will not work with GitHub Pages unless you have a GitHub Pro subscription and use custom workflows. Therefore, ensure your repo is set to public:

How to Check and Change Repository Visibility

  1. Go to your repository Settings
  2. Scroll to Danger Zone
  3. Look for “Change repository visibility”
  4. If it’s private, click Make public

Always double-check this after creation, especially if you plan to link the blog publicly.

Should You Enable GitHub Pages Build Logs

Yes. GitHub now provides better logging and error messages when your Pages site fails to deploy. Enabling this helps troubleshoot YAML errors, missing theme files, or Jekyll configuration problems.

How to Access Build Logs

Once GitHub Pages is set up:

  • Go to the Actions tab
  • Filter for the Pages build workflow
  • Click the most recent run to see logs and failure reasons

Do You Need to Add a Custom Domain at This Stage

Not yet. For now, use the default GitHub Pages subdomain. Once your site is live and working properly, you can assign a custom domain later. However, if you do want to use one:

How to Add a Custom Domain (Optional)

  1. Buy a domain from a registrar like Namecheap or Google Domains
  2. Point its DNS to GitHub Pages IPs
  3. In GitHub, go to Settings → Pages
  4. Add your domain under the “Custom domain” field

Make sure to check the box “Enforce HTTPS” if using a custom domain.

How to Write an Accurate Repository Description and Tags

Descriptions help both GitHub’s internal search and external users understand what your repo is about. Here’s how to write them effectively:

Tips for a Good Repository Description

  • Keep it short but descriptive, e.g. A minimalist blog using Jekyll and Mediumish theme
  • Use relevant topics/tags like jekyll, blog, theme, github-pages
  • Avoid vague descriptions like “My website”

Should You Add a License and README File

Yes, especially if you're using an open-source theme like Mediumish. A license clarifies usage rights, while a README file documents how to use or modify the blog. GitHub even provides templates for both.

How to Add These Files

  • Go to the main repository page
  • Click Add file → Create new file
  • For license, name it LICENSE and choose from available templates
  • For README, create README.md and write a brief guide

How to Invite Collaborators or Set Permissions

If you're working with others, set access roles to avoid accidental changes.

Steps to Add Collaborators

  1. Go to Settings → Collaborators & teams
  2. Click Add people
  3. Type the GitHub username and choose their role:
    • Admin: full access
    • Write: can push commits
    • Read: view only

How to Ensure the Repository is Ready for Theme Installation

Once you’ve configured all the above settings, the repository is now ready to install the Mediumish Jekyll theme. Make sure the following is true:

  • Public visibility is set
  • GitHub Pages is pointing to the right branch and folder
  • A README exists for clarity
  • Build logs are working and error-free

Conclusion

Setting up a GitHub repository correctly after creation is a foundational step to successfully launching a Jekyll blog, particularly with more complex themes like Mediumish. Neglecting these steps can lead to confusing errors, deployment failures, or broken websites. By following this guide, your repository will be fully optimized, clean, and ready for the next stage: installing the Jekyll theme and customizing your site.

Read more
Subscribe to: Posts (Atom)