Skip to content
PifeatureCLI & tooling1 file · +1 −0

Add GitHub sponsor button to repo

Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk

2msession
1interventions
GOAL

Add a GitHub Sponsors button to the repository by creating a FUNDING.yml file and pushing it to main.

  1. Prompt · +0
    I just want to add a sponsor button per GitHub docs to my repo.
  2. Agent did · +0m
    Checked git status, found local branch had 2 commits already squash-merged upstream, rebased onto origin/main to clean up history.
  3. Intervention · +0m
    Told the agent not to push anything else beyond the sponsor file.
    Why: I didn't want the rebase or anything else pushed automatically, just wanted to be careful.
  4. Agent did · +0m
    Checked for existing FUNDING.yml (none found) and asked which sponsor platform/links to use.
  5. Prompt · +0m
    I guess just github?
  6. Agent did · +0m
    Looked up git username, created .github/FUNDING.yml with the github key set to the user's username, and provided commit/push commands.
  7. Prompt · +1m
    Oh cool do it please
  8. Fail · +1m
    Commit and push succeeded but landed on the wrong branch (patch-1) instead of main.
  9. Agent did · +2m
    Checked out main, fast-forward merged patch-1 into it, and pushed to origin/main.
  10. Outcome · +2m
    FUNDING.yml pushed to main; sponsor button live on the repo.
VERDICT

Next time I'd tell it upfront to check the current branch before committing, since the wrong-branch commit was the only real hiccup. Catching that it was on patch-1 instead of main and fixing with a fast-forward merge is what actually got the button live. Otherwise a quick, low-effort task that mostly needed me to just confirm the sponsor platform.

I tried this · 0

Discussion · 0

How Builds work