Would just like to push for support of repository_dispatch as we are limited to not using GH Issues

[bruddy-lively]

In our current situation we are unable to utilize GH Issues as a trigger. Repository dispatch or workflow dispatch events are highly desirable for us and I imagine many others.
We have automations that we'd like to leverage, but our policies dictate that we cannot use GH Issues as a source for bug reporting etc.

[ad-m-ss]

We have a very similar situation. I've currently implemented a solution – based on Google Apps Script – to synchronize our ticket system -> GitHub issues when selected label is added, but this causes duplicates the flow of communication.

[ashwin-ant]

How does this modes concept sound? Right now our architecture makes adding dispatch event support a bit tricky since we're fairly coupled to the Claude comment. With explicit modes it should be a bit easier to shift the codebase toward supporting this sort of thing better.

[bruddy-lively]

That definitely looks more flexible. We ended up trying the claude code base action and it supported the repository_dispatch event just fine. Im not certain how related the two actions are (if at all?) but perhaps some guidance on the entry points from that action could be useful.

[ashwin-ant]

Totally! We'll likely be merging the two repos into one anyway. The base action is intended to be a barebones Claude Code SDK wrapper, and this repo is a more opinionated experience built on top of it. But to reduce confusion we're going to simplify a bit.

[bruddy-lively]

I see that the base action will stay up as a mirror, but will it be receiving updates? Basically we've moved to the base action for now, and don't want to end up being cut off from updates. We would likely move back to this action if it receives the necessary fixes to leverage repository_dispatch, but would hope that is communicated well so we can transition in a timely manner.

[ashwin-ant]

Yes we'll continue offering it as a mirror (or instruct people to use anthropics/claude-code-action/base-action@beta, which will work by default). Hoping to land this transition this week or early next week (PR is up). Nothing will break in the transition!

[ashwin-ant]

@bruddy-lively the merge is now complete. The base action repo is now a mirror of the base-action directory in this repo. Releases will be automatically kept in sync.