Merge pull request LambdaTest#1865 from amanchopra1905/stage

updated the yaml file

Author: amanchopra1905

docs/hyperexecute-how-to-manage-project-level-secrets.md

@@ -77,7 +77,7 @@ project: your-project-name
 
 # highlight-start
 env:
-  SECRET_KEY: ${{LT_SECRET_KEY}}
+  LT_SECRET_KEY: ${{.secrets.token}}
 # highlight-end
 ```
 

docs/hyperexecute-how-to-save-and-manage-secrets.md

@@ -115,21 +115,17 @@ During HyperExecute test execution, you might need to access sensitive informati
 
 Consider these secret key names: `secretKey1` and `secretKey2`.
 
-```bash
+```yaml
 version: 0.1
 env:
-  MyKey1: ${{.secrets.secretKey1}}
-
-vars:
- MyKey2: ${{.secrets.secretKey2}}
- Path: /java/files*.feature
+  MyKey1: ${{.secrets.token}}
 
- runson: win
- testDiscovery:
-   type: raw
-   mode: dynamic
-   args:
-     featureFilePath: ${Path}
+runson: win
+testDiscovery:
+  type: raw
+  mode: dynamic
+  args:
+    featureFilePath: ${Path}
 
 testRunnerCommand: npm run --username abc --password ${{.secrets.SecretKey2}}
 ```