Menu

GitHub Flow: 6 Steps, Tested With the gh CLI and Rulesets
📰

GitHub Flow: 6 Steps, Tested With the gh CLI and Rulesets

DEV Community: github·Amaresh Pelleti·27 minutes ago
#w6NRTMRA
#devtogithub#technology#devto#dev#branch
Reading 0:00
15s threshold

Originally published on DevToolHub .

GitHub flow is a branch-per-change workflow: you branch off main , push commits, open a pull request, get a review, merge, and delete the branch. GitHub's docs list exactly those six steps and no others.

I ran all six in a throwaway repository with git 2.56.0 and gh 2.103.3, then added a ruleset to see what it blocks. Below are the commands and what happened.

Step What you do Command I ran

1. Create a branch Short, descriptive name git switch -c increase-test-timeout

2. Make changes Small commits, push often git push -u origin increase-test-timeout

3. Open a pull request Draft first if you want early feedback gh pr create --draft

4. Address review comments Push more commits; the PR updates itself git push

5. Merge After approval gh pr merge --squash --delete-branch

6. Delete the branch The PR and history stay included in step 5

Open the pull request and close the issue

gh pr create --title "Increase test timeout" --body "Raises the timeout to 30s.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.