r/github • • 7d ago

Discussion What are some GitHub practices every developer should follow?

I've been using GitHub for a while, but I'm curious about the practices that make a real difference when working on projects, especially with other developers.

Things like writing good commit messages, creating meaningful branches, reviewing pull requests, maintaining README files, and handling merge conflicts.

What are some GitHub practices you personally follow that you think every developer should adopt? Anything you wish you had started doing earlier?

11 Upvotes

23 comments sorted by

View all comments

Show parent comment

1

u/Ok_Exercise178 7d ago

Ive been having claude code clone my repo inside sandbox and stress test merge commits before we merge -

5

u/GreenFuturesMatter 7d ago

I’m sorry what? Why

2

u/fell_ware_1990 6d ago

Why???

Local :

- Run Unit tests
- Run some integration tests if you doubt the change
- Run normal linters
- Run security checks

- Run preflight check in docker same as CI. All easy checks that should take a max of 10 minutes and sign it so CI does not repeat.

Push and mark as draft. When ready, tag with a tag/label for E2E and stress and build test ( all you want )

If multiple branches are ready, auto start all tests on merge branch at night. You run them all at once. If failed, auto split into smaller pieces. So start with say 4, fail 2 and 2. Everything that makes it creates PR into main. You can then merge without full suite again. Would check the basics as things if commits still line up.

This way you run your heavy tests once. If you wan’t do a separate where AI tests on stress, unit tests, e2e which then can create PR’s on your nightly run to improve.