You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can adapt workflows that are Rover built-in, or you can create workflows of your own. Custom workflows can either be saved to the global store, or local to current project. By default, workflows are added locally to the current project, but you can use the `--global` flag to refer to the global workflows when you are in a project.
97
+
98
+
Custom workflows are required to follow the [Workflow YAML file format documented here](/rover/reference/workflow-file/).
99
+
100
+
If you want to start from an existing workflow, you can first dump its contents to a file in the filesystem:
101
+
102
+
```sh
103
+
rover workflows inspect swe --raw > improved-swe.yaml
104
+
```
105
+
106
+
Make the changes you want on the `improved-swe.yaml`, and import it.
You can now refer to this workflow normally, for example:
113
+
114
+
```sh
115
+
rover task --workflow improved-swe 'Improve the installation script to check that the user has root permissions'
116
+
```
117
+
118
+
You can follow the [`Write workflows` guide](/rover/guides/write-workflows) in order to create your own workflows that accomodate your custom use cases or needs.
119
+
96
120
## Next Steps
97
121
98
122
<CardGrid>
99
123
<LinkCardtitle="Overview"href="/rover/intro/overview"description="Get started with the Rover CLI" />
100
124
<LinkCardtitle="Task"href="/rover/concepts/task"description="Learn about Rover tasks and how to manage them" />
101
125
<LinkCardtitle="Sandbox"href="/rover/concepts/sandbox"description="Understand the sandboxed environment where tasks run" />
102
126
<LinkCardtitle="Workspace"href="/rover/concepts/workspace"description="Explore the workspace where coding agents apply changes" />
0 commit comments