Hi all!<p>I wanted to share a small project that I've been working on with a buddy.<p><a href="https://www.actionspanel.app/" rel="nofollow">https://www.actionspanel.app/</a><p>One of the problems that currently exists with GitHub Actions is the fact that there is no way to easily trigger your Actions unless you cause some kind of GitHub event. This could be pushing a new commit, or creating an issue on a repository. But if you just want to run an arbitrary action, there's not currently a good way to do that.<p>This is a well known feature request:
<a href="https://github.community/t5/GitHub-Actions/GitHub-Actions-Manual-Trigger-Approvals/td-p/31504" rel="nofollow">https://github.community/t5/GitHub-Actions/GitHub-Actions-Ma...</a><p>GitHub somewhat recently added an API for `repository_dispatch` which is an available trigger for a GitHub Action. There are many blog posts that explain how you can create a Personal Access Token to send your own `repository_dispatch` via some curl command or postman request.<p>For example:
<a href="https://goobar.io/2019/12/07/manually-trigger-a-github-actions-workflow/" rel="nofollow">https://goobar.io/2019/12/07/manually-trigger-a-github-actio...</a><p>ActionsPanel uses this same API but does so with a GitHub App token so that you don't need to worry about managing your own PAT. This also makes it much easier to trigger your actions across teams with multiple people. Then you don't need to share the PAT with each other or each create your own PATs.<p>You configure your buttons with a declarative yaml file that you leave in the repo, and ActionsPanel will read that file and dynamically create your UI for you to trigger your actions.<p>We'd love to get your feedback on this project. It's very simple still but solves the core problem of triggering your actions.<p>If you do have feedback or any questions, feel free to post in this thread, or email us directly at support (at) actionspanel (dot) app<p>Looking forward to your feedback!
you can also use <a href="https://greasyfork.org/de/scripts/394032-github-deployments-and-repository-dispatch-trigger" rel="nofollow">https://greasyfork.org/de/scripts/394032-github-deployments-...</a> which adds a button for repository_dispatch event directly in your repository, no need to visit a 3party page.
I'm one of the creators of ActionsPanel. As an early adopter of GitHub Actions, this was an obvious feature gap that made it harder to switch off of other CI/CD systems (Jenkins, Circle, etc).<p>It's been great having a centralized place for all of our code and deployment related activities. The GitHub Actions ecosystem is maturing quickly and we'd like to help with that momentum.<p>--Charles
Could you also use the repository dispatch custom event? <a href="https://help.github.com/en/actions/reference/events-that-trigger-workflows#external-events-repository_dispatch" rel="nofollow">https://help.github.com/en/actions/reference/events-that-tri...</a>
My biggest problem is having to commit to test changes whilst I'm writing/debugging an action, can this help with that?
And if not, does anyone have a good solution for testing an action before committing?
If it helps im already using self hosted runners.
Nice I was looking to test this at work... But not sure if login does not work for me (and my buddy) or something else.... But we kept beeing redirected to the login button