docs(types): clarify trigger restrictions in AutomationTrigger

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 193
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/gitpod%2Fgitpod-95aec32d54661e6522d78deca8c182908b30bae1db5762b365a3ef338dbaccfa.yml
-openapi_spec_hash: cd08bb12843c15e0fe783957866deb83
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/gitpod%2Fgitpod-803e9a382bb3f4d9b6ef7b1dd12c5541bf93608d3f4c240e99054929130f260b.yml
+openapi_spec_hash: e2eae7e0a5a1fc83f3af40662b1ffbd1
 config_hash: d73914a733b27d121d59aa43bc7c710e

src/resources/shared.ts

@@ -22,8 +22,8 @@ import {
  * automation during a prebuild of an environment. This phase does not have user
  * secrets available. The `before_snapshot` field triggers the automation after all
  * prebuild tasks complete but before the snapshot is taken. This is used for tasks
- * that need to run last during prebuilds, such as IDE warmup. Note: The prebuild
- * and before_snapshot triggers can only be used with tasks, not services.
+ * that need to run last during prebuilds, such as IDE warmup. Note: The
+ * before_snapshot trigger can only be used with tasks, not services.
  */
 export interface AutomationTrigger {
   beforeSnapshot?: boolean;