{"post":{"slug":"how-to-use-github-2026","title":"How to use GitHub in 2026: from your first repo to pull requests","excerpt":"GitHub is where code lives, collaboration happens, and careers are built in 2026. Here is the practical guide from first repo to merging your first PR.","category":"code","date":"March 18, 2026","author":"ByteLedger Team","content":"<span class=\"dropcap\">G</span>itHub is where the world's code lives. Over 100 million developers use it to store projects, collaborate on teams, contribute to open source, and show off their work to employers. If you know Git basics, GitHub turns them into a full collaborative workflow. If you're still new to Git, read [Git for beginners in 2026](/blog/git-for-beginners-2026) first — this guide picks up where that one ends.\n\n## What changed in 2026\n\n- **GitHub Copilot is built into the editor** and now suggests entire functions, tests, and even PR descriptions using the context of your codebase.\n- **GitHub Actions is the dominant CI/CD tool** for most small and mid-size teams — free minutes for public repos, affordable for private.\n- **Discussions and Projects replaced many external tools.** Teams manage sprints and async conversations inside GitHub itself.\n- **The free tier is generous.** Unlimited private repos, GitHub Actions minutes (2,000/month on free), GitHub Pages hosting, and Codespaces hours.\n\n## Key concepts\n\n| Concept | What it is |\n| --- | --- |\n| Repository (repo) | A folder of code + its full Git history |\n| Fork | Your personal copy of someone else's repo |\n| Branch | An isolated line of development inside a repo |\n| Pull request (PR) | A request to merge one branch into another, with a review UI |\n| Issue | A tracked bug, feature request, or task |\n| GitHub Actions | Automated workflows that run on events (push, PR, schedule) |\n| GitHub Pages | Free static website hosting from a repo |\n\n## Creating your first repository\n\n1. Click **New** on GitHub.com.\n2. Name it (e.g. `my-first-project`), choose Public or Private, check **Add a README**.\n3. Clone it locally:\n\n```bash\ngit clone https://github.com/yourusername/my-first-project.git\ncd my-first-project\n```\n\n4. Make changes, commit, push:\n\n```bash\necho \"# Hello GitHub\" >> README.md\ngit add README.md\ngit commit -m \"docs: update README\"\ngit push origin main\n```\n\n## Opening a pull request\n\nPRs are the core collaboration unit in GitHub. Even on solo projects, they create a reviewable history.\n\n```bash\n# Create a branch for your change\ngit checkout -b feat/add-contact-page\n\n# Make changes, then commit\ngit add .\ngit commit -m \"feat: add contact page with form\"\n\n# Push the branch to GitHub\ngit push origin feat/add-contact-page\n```\n\nGitHub will show a yellow banner: \"Compare & pull request.\" Click it, write a description, and open the PR. On a team, someone reviews and approves; then you merge and delete the branch.\n\n## GitHub Actions: automate everything\n\nGitHub Actions runs automated workflows on your repo. The most common: run tests on every push.\n\nCreate `.github/workflows/test.yml`:\n\n```yaml\nname: Run Tests\n\non: [push, pull_request]\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions/checkout@v4\n      - uses: actions/setup-python@v5\n        with:\n          python-version: '3.12'\n      - run: pip install pytest\n      - run: pytest\n```\n\nEvery push now runs your tests automatically. Failed checks block merging the PR — this is the foundation of safe collaborative development.\n\n## Building a GitHub profile that gets noticed\n\nYour GitHub profile is a live portfolio. What hiring managers look at:\n\n| Signal | What it shows |\n| --- | --- |\n| Pinned repositories | Your best work, intentionally highlighted |\n| Contribution graph | Consistency and activity over time |\n| README.md on repos | Communication ability; can you explain what you built? |\n| Commit history | Granular view of how you work |\n| Stars and forks | Community validation of open-source work |\n\nWrite a profile README: create a repo named exactly `yourusername` and its README.md appears on your profile page.\n\n## Contributing to open source\n\nOpen source contributions are the fastest way to demonstrate real-world collaboration skills.\n\n1. **Find beginner issues** — filter by `good first issue` or `help wanted` labels on any large repo.\n2. **Fork the repo**, clone your fork, and create a branch.\n3. **Make the smallest possible change** that solves the issue.\n4. **Open a PR to the original repo** — describe what you did and why.\n5. **Respond to review comments** — this is the collaboration part.\n\nEven a documentation fix or test addition counts. First PRs merged to active projects look great on a resume.\n\n## GitHub vs the alternatives\n\n| Platform | Best for |\n| --- | --- |\n| GitHub | Default; largest community and ecosystem |\n| GitLab | Self-hosted teams; built-in DevOps pipeline |\n| Bitbucket | Atlassian shops (Jira integration) |\n| Codeberg | Open-source only, privacy-focused |\n\nFor most developers in 2026, GitHub is the right choice — the network effects and integration surface are unmatched.\n\n## Common mistakes\n\n**Keeping repos private when there's no reason to.** Public repos build your portfolio. Make projects public unless they contain secrets.\n\n**Committing secrets to a public repo.** GitHub scans for exposed API keys and notifies providers — but the key is already compromised. Use `.gitignore` and environment variables.\n\n**Never writing PR descriptions.** A blank PR wastes your reviewer's time and yours. Two to three sentences on what changed and why is the minimum.\n\n**Ignoring failed Actions.** If your CI fails, fix it before merging. \"It'll be fine\" technical debt accumulates fast.\n\n## What to skip\n\n- **GitHub Desktop for all your interactions** — the web UI and CLI teach you what's actually happening; the GUI client is fine but don't rely on it exclusively.\n- **Squashing every commit blindly** — preserve commit history that tells a story; only squash \"wip\" and \"fix typo\" noise.\n- **Ignoring Issues for solo projects** — tracking bugs and features even for yourself builds the habit and makes projects easier to resume after a break.\n\n## FAQ\n\n**Is GitHub free?**\nThe free tier is generous: unlimited public and private repos, 2,000 Actions minutes/month, GitHub Pages, and GitHub Copilot free for students and open-source maintainers.\n\n**What's the difference between a fork and a branch?**\nA branch lives inside the same repo. A fork is a complete copy of the repo in your own GitHub account — used when you don't have write access to the original.\n\n**How do I undo a merge on GitHub?**\nOpen the merged PR, click **Revert** — GitHub creates a new PR that reverses the changes. The original commit history is preserved.\n\n**How many repos should I have in my portfolio?**\nThree to five strong, complete projects with good READMEs beat twenty half-finished stubs. Quality over quantity.\n\n## Where to go next\n\nSee [Git for beginners in 2026](/blog/git-for-beginners-2026), [How to become a software engineer in 2026](/blog/how-to-become-a-software-engineer-2026), and [How to deploy a web app in 2026](/blog/how-to-deploy-a-web-app-2026).","hue":315,"metaTitle":"How to Use GitHub in 2026: Repos, PRs, and Actions","metaDescription":"How to use GitHub in 2026 — create repos, open pull requests, use GitHub Actions for CI, and build a portfolio profile that gets noticed.","keywords":["how to use github 2026","github tutorial for beginners 2026","github pull request explained","github actions tutorial 2026","github profile portfolio 2026","open source contribution github","github vs gitlab 2026","github repository beginner","how to contribute to open source 2026","github workflow tutorial"],"tldr":["**GitHub is not Git** — Git is the version control tool; GitHub is the hosting platform that adds collaboration, CI/CD, and project management.","**Your GitHub profile is a portfolio** — consistent green squares and quality READMEs matter to hiring managers and clients.","**Pull requests are how code gets reviewed** — open a PR for every change, even on solo projects; it builds the habit.","**GitHub Actions automate everything** — tests, deploys, and lint checks run automatically on every push for free.","**Skip:** committing directly to main on shared repos; all meaningful work should flow through a PR so it can be reviewed and reverted cleanly."],"readTime":"5 min read","wordCount":1093},"related":[{"slug":"what-is-a-git-fork-2026","title":"What Is a Git Fork in 2026: copies and contributions","excerpt":"A fork is your own server-side copy of someone elses repository, hosted on GitHub or a similar platform, that lets you change a project freely and propose those changes back through a pull request.","category":"code","date":"June 9, 2026","author":"ByteLedger Team","readTime":"4 min read","hue":200},{"slug":"how-to-contribute-to-open-source-2026","title":"How to Contribute to Open Source in 2026: a beginner path","excerpt":"The realistic way to contribute to open source in 2026 is to start with docs and small fixes on a project you actually use, then work up to code. Here is the full path.","category":"code","date":"May 15, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":240},{"slug":"what-is-a-pull-request-2026","title":"What is a pull request in 2026? How code review works on Git","excerpt":"A pull request is a proposal to merge your code changes into a shared branch, with built-in review. This guide explains how pull requests work and how to open a good one in 2026.","category":"code","date":"June 10, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":268}],"sameCategory":[{"slug":"bazel-build-explained-2026","title":"Bazel Explained: What Hermetic Builds Actually Cost","excerpt":"Bazel delivers reproducible, precisely cached builds and demands that you describe everything. Here is what you get, what it costs, and who should say no.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":145},{"slug":"graphql-federation-2026","title":"GraphQL Federation: One Graph, Many Teams","excerpt":"Federation composes independently-owned subgraphs into a single API. Here is what it solves, the operational cost it adds, and when a simpler gateway is enough.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":300},{"slug":"hermetic-builds-explained-2026","title":"Hermetic Builds Explained: Same Inputs, Same Output","excerpt":"A hermetic build depends only on declared inputs. Here is what that property gives you, the common leaks that break it, and how to move toward it incrementally.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":130},{"slug":"monorepo-tooling-compared-2026","title":"Monorepo Tooling Compared: What You Actually Need","excerpt":"Monorepo tools solve task orchestration and caching, not repository layout. Here is what each tier provides and how to tell when you have outgrown the simple option.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":150}],"newer":{"slug":"how-to-use-flux-image-2026","title":"How to use Flux image generation in 2026: models, prompts, and workflows","excerpt":"Flux is the open-weight challenger that now rivals closed models on prompt adherence and resolution. Here is how to run it, prompt it, and get production results.","category":"ai","date":"March 18, 2026","author":"ByteLedger Team","readTime":"4 min read","hue":215},"older":{"slug":"how-to-use-mistral-2026","title":"How to use Mistral AI in 2026: models, API, and local setup","excerpt":"Mistral AI has one of the strongest open-weight model lineups in 2026. Here is how to access, configure, and get the most out of Mistral models.","category":"ai","date":"March 18, 2026","author":"ByteLedger Team","readTime":"4 min read","hue":210}}