Github Pr Workflow — GitHub PR lifecycle: branch, commit, open, CI, merge
Github Pr Workflow — GitHub PR lifecycle: branch, commit, open, CI, merge
Start with meaning, then move to detail.
This lesson explains Github Pr Workflow — GitHub PR lifecycle: branch, commit, open, CI, merge as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Prerequisites, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Github Pr Workflow — GitHub PR lifecycle: branch, commit, open, CI, merge without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
GitHub PR lifecycle: branch, commit, open, CI, merge
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Prerequisites
Read this after the foundation, then connect it to the previous step.
- 04Quick Auth Detection
Read this after the foundation, then connect it to the previous step.
- 05Extracting Owner/Repo from the Git Remote
Read this after the foundation, then connect it to the previous step.
- 061. Branch Creation
Read this after the foundation, then connect it to the previous step.
- 072. Making Commits
Read this after the foundation, then connect it to the previous step.
- 083. Pushing and Creating a PR
Read this after the foundation, then connect it to the previous step.
- 09Push the Branch (same either way)
Read this after the foundation, then connect it to the previous step.
- 10Create the PR
Finish here to verify the result and special cases.
Copy only after you understand the effect.
# Determine which method to use throughout this workflow
if command -v gh &>/dev/null && gh auth status &>/dev/null; then
AUTH="gh"
else
AUTH="git"
# Ensure we have a token for API calls
if [ -z "$GITHUB_TOKEN" ]; then
if _hermes_env="${HERMES_HOME:-$HOME/.hermes}/.env"; [ -f "$_hermes_env" ] && grep -q "^GITHUB_TOKEN=" "$_hermes_env"; then
GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" "$_hermes_env" | head -1 | cut -d= -f2 | tr -d '\n\r')
elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
GITHUB_TOKEN=$(uv run python3 "${HERMES_HOME:-$HOME/.hermes}/skills/github# Works for both HTTPS and SSH remote URLs
REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*github\.com[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)
echo "Owner: $OWNER, Repo: $REPO"# Make sure you're up to date
git fetch origin
git checkout main && git pull origin main
# Create and switch to a new branch
git checkout -b feat/add-user-authenticationRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.