feat:example github flow guide added

[Prat011]

Important

Adds a guide for listing GitHub branches using Composio tools, with steps for dashboard, CLI, Python, and JavaScript.

• Documentation:
  • Adds example-flow-github.mdx to provide a guide on listing all branches in a GitHub repository.
  • Includes steps for using the dashboard, CLI, Python, and JavaScript to find and execute actions.
• Configuration:
  • Updates mint.json to include the new guide in the navigation under patterns/actions/example-flow-github.

^{This description was created by for 1f3935c. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
composio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 29, 2024 0:02am

[sweep-ai]

Hey @Prat011, here is an example of how you can ask me to improve this pull request:

@Sweep Add unit tests for the `find_actions_by_use_case` method in Python to verify it correctly filters GitHub actions based on use case strings.

📖 For more information on how to use Sweep, please read our documentation.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 678a967 in 15 seconds

More details

• Looked at 330 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. docs/patterns/actions/example-flow-github.mdx:153

• Draft comment:
  Consider using let or const instead of var for variable declaration to avoid potential scope issues.

let resp = response.choices[0].message.tool_calls 

• Reason this comment was not posted:
  Confidence changes required: 50%
  The JavaScript code uses 'var' for variable declaration, which is outdated and can lead to scope issues. 'let' or 'const' should be used instead.

2. docs/patterns/actions/example-flow-github.mdx:238

• Draft comment:
  Consider using let or const instead of var for variable declaration to avoid potential scope issues.

let resp = response.choices[0].message.tool_calls 

• Reason this comment was not posted:
  Confidence changes required: 50%
  The JavaScript code uses 'var' for variable declaration, which is outdated and can lead to scope issues. 'let' or 'const' should be used instead. This issue appears again in the full code section.

Workflow ID: wflow_sAHhIjCH3bkie3Gv

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[github-actions]

This comment was generated by github-actions[bot]!

JS SDK Coverage Report

📊 Coverage report for JS SDK can be found at the following URL:
https://pub-92e668239ab84bfd80ee07d61e9d2f40.r2.dev/coverage-11554583254/coverage/index.html

📁 Test report folder can be found at the following URL:
https://pub-92e668239ab84bfd80ee07d61e9d2f40.r2.dev/html-report-11554583254/html-report/report.html

[ellipsis-dev]

👍 Looks good to me! Incremental review on 1f3935c in 34 seconds

More details

• Looked at 463 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 7 drafted comments based on config settings.

1. docs/introduction/foundations/components/list_local_tools.mdx:93

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Comment did not seem useful.

2. docs/introduction/foundations/components/list_local_tools.mdx:129

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Marked as duplicate.

3. docs/introduction/foundations/components/list_local_tools.mdx:174

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Marked as duplicate.

4. docs/introduction/foundations/components/list_local_tools.mdx:217

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Marked as duplicate.

5. docs/introduction/foundations/components/list_local_tools.mdx:247

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Marked as duplicate.

6. docs/introduction/foundations/components/list_local_tools.mdx:293

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Marked as duplicate.

7. docs/introduction/foundations/components/list_local_tools.mdx:314

• Draft comment:
  The action identifier should be a single action, not a list. Also, ensure the correct action identifier is used for each task. For example, Action.BROWSERTOOL_CLICK_ELEMENT for clicking an element.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_Njye2lnUvBljRMqL

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.