EditorOpsDevOps automation for your code editor. Save time and eliminate context switches. Start automating your development workflows—right inside your code editor. ⚡ Switch Slack to Do Not Disturb when in flow ⚡ Set a custom Slack status when your editor is focused ⚡ Play your most productive Spotify playlist when in flow ⚡ And much more... Getting StartedMake your code editor work for you. With EditorOps, we envision a smarter code editor that helps you make daily work faster, more efficient, and more enjoyable.
Creating WorkflowsTo create your first workflow, select the EditorOps icon in the sidebar. Follow the instructions in your editor to create a Software account to get started. Once you've created an account, return to your code editor and you will be signed into your new account. You can create automations using built-in templates, which allow you to get started using popular workflows. Currently, there are two templates available. You can also design your own workflows by selecting triggers and actions. To create a custom workflow from scratch, click TriggersFirst, select a trigger for your automation. Triggers are events that start an automation.
ActionsNext, select actions for your automation. Actions are events that happen in response to a trigger. Each trigger can have multiple actions.
After creating your workflow with triggers and actions, you will be able to see all your active automations in the EditorOps sidebar. When you click on an automation, you can update, rename, or delete it. IntegrationsStart automating your workflows by connecting your favorite tools. Discover new and remarkable ways to improve your daily work with integrations to Google Calendar, Microsoft Outlook, Slack, and more.
Community WorkflowsExplore awesome workflows built by our community of over 150,000 developers.
Share Your FeedbackEnjoying EditorOps? Let us know how it's going by tweeting or following us at @software_hq. Have any questions? Create an issue in the EditorOps project on GitHub or send us an email at support@software.com and we'll get back to you as soon as we can. It’s Safe, Secure, and FreeWe never access your code: We do not read, transmit, or store source code. We only provide metrics about programming and automate workflows from those metrics, and we make it easy to see the data we collect. You can learn more about how we secure your data on our security page. Your data is private: We will never share your individually identifiable data with anyone. Free for you, forever: We provide 90 days of data history for free, forever. We provide premium plans for advanced features and historical data access. Editor Ops also collects basic usage metrics to help us make informed decisions about our roadmap. Data collected and purpose | Data Collected | Purpose of Data | | -------------- | --------------- | | Local Timezone | Applying time zones to aggregate metrics so that daily values are accurate | | Hostname | Used for de-duplicating accounts and linking multiple installations together under same login. Hostname is hashed before usage | | File open, save, close events | These events are used to capture general activity within the editor and extend code time sessions | | Editor focus / unfocus | These events are used to capture general activity within the editor and extend code time sessions | | Document change events | These events are used to characterize what types of changes are being made to a document. CONTENT OF A DOCUMENT IS NEVER STORED OR TRANSMITTED | | Project directory | Used to segment activity and Code Time across projects | | Git Repo Name | Used to segment activity and Code Time across git repos (Can be turned off in settings) | | File name | Used to segment activity and Code Time across file names (File names are one-way hashed before use) | |