Skip to content

robostack-bot: pinning update commits carry [ci skip] - #121

Open
Tobias-Fischer wants to merge 1 commit into
mainfrom
bot-pinning-ci-skip
Open

Tobias-Fischer wants to merge 1 commit into
mainfrom
bot-pinning-ci-skip

Conversation

@Tobias-Fischer

Copy link
Copy Markdown
Collaborator

The bot's daily update-conda-forge-pinning run re-creates its commit on top of main and force-pushes it (that's how peter-evans/create-pull-request updates a PR), so the pinning PR (#94) restarts its build every day, and a pinning update can rebuild a lot.

Now the commit message of pinning updates ends in [ci skip] (the PR title stays the same), so those pushes don't start CI. To build such a PR, push any commit without the marker, e.g. git commit --allow-empty -m "Build". The README's bot table says so too. Other bot commands are unchanged.

The schedule runs the default branch's bot.yaml, so this takes effect once merged; until then the next daily run will push #94 again and start a build.

🤖 Generated with Claude Code

create-pull-request re-creates the bot's commit on top of main on every
run and force-pushes it, so the daily update-conda-forge-pinning run
restarted the PR's build (which can rebuild a lot) every day. Its commits
now carry [ci skip]; to build such a PR, push a commit without the marker.
The PR title stays as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Tobias-Fischer

Copy link
Copy Markdown
Collaborator Author

This is ready for review :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants