Thanks so much for all the awesome feedback we've received so far! We've taken your suggestions to heart and have added a "Coming Soon" section to our documentation to share some of the exciting features we're working on. Special shoutout to Arbortheus!
We'd love to keep hearing from you! Your feedback helps us prioritize what matters most.
You're absolutely right—right now, Actionate focuses on running and managing GitHub Actions within the IDE. We chose this initial feature set as a foundation to build more advanced capabilities, like the ones you're describing. Our goal was to get an early version out to gather feedback from users like you, so we can prioritize features that truly matter rather than relying solely on our assumptions.
The next major feature we're working on is the ability to manage Actions Environments, Variables, and Secrets directly from the IDE. Not only will you be able to manage these values effortlessly, but Actionate will also provide intelligent auto-complete for workflow files by leveraging this data. No more worrying about fat-fingering a hardcoded string again—Actionate will offer native IDE suggestions for environments, variables, and secrets, all based on the currently set environment in your workflow file.
We have several other exciting features in the pipeline and can't wait to bring them to life. Your feedback is incredibly valuable in helping us decide what to prioritize next—so please keep it coming!
Thank you so much for your interest! We’ve definitely thought about supporting multiple CI providers, including GitLab, and your feedback helps us prioritize future features. We truly appreciate it and will keep it in mind as we continue to grow. Thanks again for your support!
Thank you so much for your feedback—it’s truly valuable to us. We do our best to test thoroughly before releasing, but we know we can’t anticipate every scenario. The issues you’ve highlighted are extremely helpful, and we’ll be prioritizing them in our next release.
Regarding the error you encountered after installing the plugin and connecting your GitHub account—"The plugin io.revenate.actionate failed to save settings. Please restart GoLand"—this does appear to be a false positive. Behind the scenes, we use the built-in IDE mechanisms to persist the selected GitHub account, and sometimes the IDE throws this error when attempting to save the settings file for the first time. This happens because the IDE tries to back up the settings file before persisting changes, and intermittently fails to detect that the file doesn’t exist yet. We’ve already reported this issue to JetBrains.
As for your feedback about the lack of search functionality and scrollbar behavior in step logs, you're absolutely right—log search is a critical feature, and it's planned for the very next release. Regarding the scrollbar, our UI leverages the JetBrains embedded JCEF (Chromium-based) browser, and its behavior can vary depending on the IDE version. In some versions, the scrollbar is always present, while in others it only appears when scrolling. This behavior is controlled by the underlying JCEF implementation, and we’ve also raised this issue with JetBrains.
We sincerely appreciate you taking the time to share your thoughts, and your feedback helps us improve Actionate to better serve our users. Please keep the suggestions coming—we love hearing from you!
Thanks for pointing that out! It seems this issue is related to how the in-IDE plugin marketplace search is implemented. For some reason, searching for "Actionate" doesn't return the expected result, but if you search for "Actionat" (without the final "e"), the plugin does show up.
We’re looking into this and will reach out to JetBrains to better understand the search behavior. In the meantime, you can also find Actionate directly on the JetBrains Marketplace.
Thanks again for bringing this to our attention—we really appreciate it!
Our MVP release focuses on bringing most, if not all, GitHub Actions functionality directly into JetBrains IDEs, allowing users to manage their workflows without leaving their development environment. The primary value here is reduced context switching, leading to increased productivity and uninterrupted focus—something we as developers deeply appreciate.
That said, this is just the beginning. Our long-term vision goes beyond simple UI integration—we aim to introduce features that expand what's possible with GitHub Actions, such as the ability to run actions locally or seamlessly set up your local machine as a GitHub self-hosted runner. This would allow developers to test workflows for free during development, using the same setup they rely on in production.
And that's just one example! We have plenty more ideas and would love to hear from the community about what features would make GitHub Actions even more powerful inside JetBrains IDEs.
We’re excited about the journey ahead and appreciate your feedback!
We'd love to keep hearing from you! Your feedback helps us prioritize what matters most.
Check out the new section here: https://github.com/revenate/actionate?tab=readme-ov-file#-co...