Most developers use GitHub every week, but many only touch the obvious features: pushing code, opening pull requests, and browsing files. GitHub has a deeper set of shortcuts, URL tricks,# 10 Useful GitHub Tricks Most Developers Don’t Know
Most developers use GitHub every week, but many use only a small fraction of what the platform can actually do. Beyond repositories, commits, and pull requests, GitHub includes shortcuts, URL tricks, formatting features, and workflow tools that can save time, improve collaboration, and make navigation much faster.
The best part is that many of these tricks are simple. You do not need a big team, paid tools, or complex setup to benefit from them; in many cases, a single keyboard shortcut or small workflow change can make GitHub noticeably more productive.
1. Press t to find files fast
One of the most useful hidden shortcuts on GitHub is the fuzzy file finder. When you are inside a repository, pressing t opens a file search interface that lets you jump directly to files by typing part of the name instead of manually clicking through folders.
This is especially helpful in large projects where browsing the directory tree is slow. If you are trying to understand a new codebase, jumping straight to files like package.json, schema.rb, Dockerfile, or settings.py is much faster than drilling through the UI.
2. Link directly to code lines
GitHub lets you link to a specific line of code just by clicking a line number while viewing a file. The URL updates with a line reference such as #L1337, and you can also select a range of lines by holding Shift and clicking another line number.
This is one of the most valuable tricks for code reviews, documentation, bug reports, and technical discussions because it lets you point directly to the exact code being discussed. GitHub also notes that if you want a stable canonical version of that link, you can press y or use the permalink option so the URL keeps working even if the branch changes later.
3. Use y to create a permanent link
Many developers share file URLs from a branch view without realizing that those links may later point to different code if the branch keeps moving. GitHub provides a simple fix: press y while viewing a file, and the URL is converted into a canonical permalink tied to that specific version of the file.
This is a small trick with a big payoff. It is ideal when you are referencing code in blog posts, support tickets, documentation, or team messages where you need the exact version to remain stable over time.
4. Improve docs with hidden Markdown features
GitHub Flavored Markdown supports more than basic headings and bullet points. GitHub’s own pro tips highlight several useful HTML-enhanced Markdown features, including <kbd> tags for keyboard keys, <details> and <summary> for collapsible sections, <sup> and <sub> for smaller text, and centered content using aligned <div> blocks.
These features are especially useful in READMEs and technical docs. For example, collapsible sections are perfect for long logs or debug output, while <kbd> tags make shortcut instructions much clearer in setup guides and tutorials.
5. Show diffs inside Markdown
GitHub also supports syntax highlighting for fenced code blocks when you specify a language, and one clever example is diff. If you label a fenced block as diff, removed lines are highlighted differently from added lines, creating a readable mini visual diff inside documentation or comments.
That makes this trick useful for changelogs, migration guides, documentation updates, and teaching examples. Instead of describing a change only in prose, you can show readers exactly what changed in a way that feels familiar to anyone who has reviewed code before.
6. Combine topic pages with URL tricks
GitHub topic pages are useful for discovering projects, but the interface mainly exposes filtering by one topic and sometimes language. GitHub’s pro tips show that you can combine topics by appending a query parameter to a topic URL, which makes it possible to find repositories that match more specific combinations like one topic plus another keyword or subject area.
This is valuable when exploring ecosystems or researching tools. For example, if you want projects around a niche such as visualization inside a broader topic, this kind of URL-based filtering can surface better results than broad search alone.
7. Turn your profile into a portfolio
GitHub can display a custom profile README if you create a public repository with the exact same name as your username and place a README.md file in the root. GitHub documents that this README then appears on your profile page, effectively turning your profile into a personal landing page.
This is an underrated trick because it gives developers a simple way to showcase projects, skills, writing, links, and status updates without creating a separate website. It is especially useful for freelancers, job seekers, open-source maintainers, and anyone who wants their GitHub presence to be more intentional.
8. Use GitHub CLI for faster workflows
GitHub’s documentation for Actions secrets includes examples using the GitHub CLI, such as gh secret set SECRET_NAME and gh secret list, which shows how many repository tasks can be handled directly from the terminal instead of the browser.
This matters because once you adopt the CLI, GitHub starts fitting more naturally into terminal-based development workflows. Managing secrets, pull requests, issues, and repository operations from the command line can reduce context switching and speed up repetitive tasks.
9. Secure automation with GitHub Actions secrets
A common mistake in CI workflows is hardcoding tokens or credentials into files. GitHub provides repository, environment, and organization-level secrets for GitHub Actions, and the docs explicitly support managing them through the interface or the GitHub CLI.
This is not just a security best practice; it is also a practical productivity trick. Once your workflows rely on proper secrets management, you can automate deployments, API calls, and integrations safely without exposing credentials in your repository history.
10. Use insights and contributor metrics intelligently
GitHub’s pro tips also highlight command-line ways to analyze repository contribution data, such as git shortlog -sn to generate an ordered list of authors by commit count, with --no-merges available to exclude merge commits. The same post also references tools like git-quick-stats, git-fame, and git-stats for broader contribution analysis.
These metrics should not be treated as a full measure of engineering value, but they are useful for understanding repository history, spotting maintenance patterns, and quickly getting context on who has contributed most heavily to a project. Used carefully, they can help with onboarding, audits, and open-source evaluation.
Where these tricks help most
These tricks are most useful in a few recurring scenarios:
- Exploring unfamiliar repositories faster with keyboard navigation and file search.
- Writing better documentation with richer Markdown formatting and stable code links.
- Improving collaboration through precise references and cleaner automation.
- Turning a normal GitHub account into a stronger professional presence through a profile README.
What makes them valuable is not that they are flashy, but that they remove friction from everyday work. Most developers already live in GitHub, so even small improvements compound quickly over weeks and months.
A practical setup
If you want to put these tricks into use immediately, start with a small routine:
- Use
twhenever you enter an unfamiliar repository. - Use line links and
ypermalinks whenever you reference code in chat, issues, or docs. - Upgrade your README files with
<details>,<kbd>, and syntax-highlighted code blocks. - Create a profile README if you have not done so already.
- Move workflow credentials into GitHub Actions secrets and manage them with
gh.
That combination alone makes GitHub feel much more powerful without requiring advanced setup. It also improves how you navigate, communicate, document, and present your work.
GitHub rewards people who go a little deeper than the basics. Once you start using these lesser-known tricks, the platform stops feeling like just a place to host code and starts working more like a high-leverage developer environment.