Git · medium
The promo banner was committed on release by mistake. It belongs on feature/promo-banner, which still points to the base that release had before the slip. The work is good; only the branch tip is in the wrong place.
Put the banner commit on feature/promo-banner, then leave release at one commit. Finish on the feature branch with a clean working tree.
repo/
└── src/
└── banner.ts (committed on release by mistake)With sharpen installed, this command opens exactly this challenge in your local arena:
sharpen 12
First time? The full install is right below.
npm install -g @juanwmedia/sharpen sharpen 12 npx @juanwmedia/sharpen 12 sharpen update