Adding docs (#14597)

* docs for environment variables in private components

* warning in subscriptions api for git synced projects

* update description

* update

* update

Author: andrewjschuang

docs-v2/pages/environment-variables.mdx

@@ -114,6 +114,10 @@ You can reference the value of environment variables using `{{process.env.YOUR_E
   src="https://res.cloudinary.com/pipedreamin/image/upload/v1708551738/env-vars-feb-2024/env-vars-object-explorer-v2_x9afzl.png"
 />
 
+<Callout type="info">
+  [Private components](https://pipedream.com/docs/components#using-components) (actions or triggers) do not have direct access to workspace or project variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable.
+</Callout>
+
 ## Frequently Asked Questions
 
 ### What if I define the same variable key in my workspace env vars and project env vars?

docs-v2/pages/rest-api/index.mdx

@@ -157,8 +157,8 @@ The response from the request above will have a shape that looks like:
 Pipedream uses conventional HTTP response codes to indicate the success or
 failure of an API request:
 
-- Codes in the `2xx` range indicate success. 
-- Codes in the `4xx` range indicate an error that failed (e.g., a required parameter was omitted). 
+- Codes in the `2xx` range indicate success.
+- Codes in the `4xx` range indicate an error that failed (e.g., a required parameter was omitted).
 - Codes in the `5xx` range indicate an error with Pipedream's server.
 
 ## Accounts
@@ -1073,6 +1073,10 @@ DELETE /sources/{id}
 
 ## Subscriptions
 
+<Callout type="warning">
+  The Subscriptions API is currently incompatible with projects that have [GitHub Sync](https://pipedream.com/docs/projects/git) enabled. To [trigger another workflow](https://pipedream.com/docs/code/nodejs#invoke-another-workflow), use `$.flow.trigger` instead.
+</Callout>
+
 ### Listen for events from another source or workflow
 
 You can configure a source or workflow to receive events from any number of