-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Format issue in README #65
Comments
Hi, I want to contribute in this issue.. |
Please. It's assigned to you. |
should I append those informations in one section or in separate 3 section ? |
@qingyun-wu could you suggest? Also, could you preview the doc before you approve a doc change? |
Hello @sonichi I came across issue #65 regarding the formatting problem in the README. I've reviewed the conversation and understand that there's a need to format a paragraph as sub-bullet points. I'm super interested in contributing to this project and would like to offer my assistance if @Itsbabin requires any help or if there are other related tasks. |
@alhridoy please help me. I can't understand in which section I should write? |
Please help me in my first open-source contribution |
I have created a PR, which resolves this issue. Kindly do check this @sonichi. |
* initial pipeline * setting branches * renaming workflow to workflows * no needed permissions for building * testing pipeline * testing pipeline * testing pipeline * tweak marketing workflow * tweak paths * change to pwsh * updating run-names * trying if I can pass --no-state as a param * setting --no-state second try * renaming * powershell * add PR number to the run-name * run-name * run name test # 2000 * Confident that this will be the last try --------- Co-authored-by: Kosta Petan <kostapetan@gmail.com>
…up Chat (microsoft#65) * Changes to support custom model client class for auto speaker selection group chats * Documentation added --------- Co-authored-by: Qingyun Wu <qingyun0327@gmail.com>
A recent PR introduce a paragraph with some formatting issue:
Multi-agent conversations: AutoGen agents can communicate with each other to solve tasks. This allows for more complex and sophisticated applications than would be possible with a single LLM. Customization: AutoGen agents can be customized to meet the specific needs of an application. This includes the ability to choose the LLMs to use, the types of human input to allow, and the tools to employ. Human participation: AutoGen seamlessly allows human participation. This means that humans can provide input and feedback to the agents as needed.
They are supposed to be sub bullet points. A fix is appreciated.
The text was updated successfully, but these errors were encountered: