You use GitHub every day. But you’re probably missing features that would save you real time.

1. Code Search with regex

GitHub’s code search supports regex, language filters, and path filters. Way more powerful than Ctrl+F.

/useState\(\w+\)/ language:typescript path:src/

Find every useState call in TypeScript files under src/. You can also search by file size, repo, org, and symbol type.

Go to github.com/search and switch to “Code” tab.

2. Saved Replies

If you write the same PR review comments over and over (“Please add tests,” “Missing error handling,” “Needs a changelog entry”), save them.

Settings → Saved replies. Then in any comment box, click the arrow icon to insert a saved reply. Cuts repetitive review time in half.

3. CODEOWNERS

Define who must review changes to specific files. Put a CODEOWNERS file in your repo root:

# Frontend team owns all React code
*.tsx @frontend-team
*.css @frontend-team

# Backend team owns API routes
/src/api/ @backend-team

# Security team must review auth changes
/src/auth/ @security-team

PRs that touch these paths automatically request reviews from the right people. No more “who should review this?“

4. Autolinked References

Settings → Autolinked references. Map patterns to URLs so references in issues and PRs become clickable links.

Prefix: JIRA-
URL: https://yourcompany.atlassian.net/browse/JIRA-<num>

Now every mention of JIRA-1234 in any issue, PR, or comment becomes a clickable link to your Jira ticket.

5. Required Workflows

Organization-level workflows that run on every repo. Set up a security scan, license check, or code quality gate once, and it applies to every repo in your org.

Settings → Actions → Required workflows. Select the workflow and which repos it applies to.

6. .github Repository

Create a repo called .github in your org. Files in it become defaults for all repos:

• ISSUE_TEMPLATE/ — default issue templates
• PULL_REQUEST_TEMPLATE.md — default PR template
• FUNDING.yml — sponsor button config
• profile/README.md — your org’s profile page

Set it up once, every new repo inherits it.

7. Keyboard Shortcuts

Press ? on any GitHub page to see all shortcuts. The most useful:

.         → Open repo in github.dev (VS Code in browser)
t         → File finder (fuzzy search)
s or /    → Focus search bar
g + n     → Go to notifications
g + c     → Go to code tab
g + i     → Go to issues tab
g + p     → Go to pull requests tab

The . shortcut alone is worth knowing — it opens a full VS Code editor in your browser for quick edits without cloning.

---

Start with CODEOWNERS and saved replies. They take 5 minutes to set up and save time on every PR from that point on.

Related: Git cheat sheet · GitHub Actions cheat sheet · 10 GitHub Actions That Save Hours · 7 Vscode Extensions Cant Live Without · 12 Websites Every Developer Should Bookmark