-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Changes in README.md #3838
base: main
Are you sure you want to change the base?
Changes in README.md #3838
Conversation
- Corrected typos and improved clarity in important notes. - Enhanced formatting for key features, installation instructions, and API layering. - Standardized language throughout the document for better readability. - Updated URLs and code snippets for accuracy.
- Corrected typos and improved clarity in important notes. - Enhanced formatting for key features, installation instructions, and API layering. - Standardized language throughout the document for better readability. - Updated URLs and code snippets for accuracy.
- Corrected typos and improved clarity in important notes. - Enhanced formatting for key features, installation instructions, and API layering. - Standardized language throughout the document for better readability. - Updated URLs and code snippets for accuracy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some good edits here - but can you please revert the changes where you are condensing multiple lines into 1. This makes the diff unnecessarily large and hard to see the content changes.
Co-authored-by: Jack Gerrits <[email protected]>
@microsoft-github-policy-service agree |
There are still a large number white space and new line changes, can you please revert those |
I still see many changes around removing new lines that are not needed for the proposed content changes. For example the entire legal section. If you would like to resolve all such changes then we can consider this PR. |
We are aware that there are thousands of forks of AutoGen, including many for personal development and startups building with or on top of the library. We are not involved with any of these forks and are not aware of any plans related to them. | ||
https://github.com/microsoft/autogen/ remains the only official repo for development and support of AutoGen. | ||
We are aware that there are thousands of forks of AutoGen, including many for personal development and startups building with or on top of the library. | ||
We are not involved with any of these forks and are not aware of any plans related to them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we not have these new line edits (this and many others in this PR) if there is not edit to the context. Thanks!
Our current plan is to enable an implementation of AutoGen Studio | ||
on the AgentChat high level API which implements a set of agent functionalities | ||
(agents, teams, etc). | ||
|
||
### How do I migrate? | ||
|
||
For users familiar with AutoGen, the AgentChat library in 0.4 provides similar concepts. | ||
We are working on a migration guide. | ||
For users familiar with AutoGen, the AgentChat library in 0.4 provides similar concepts. We are working on a migration guide. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert these new line edits, and many other ones in this file. Thanks!
Why are these changes needed?
These changes are necessary to improve the overall clarity, consistency, and professionalism of the README.md documentation for the AutoGen project. The modifications include correcting grammatical errors, fixing typos, and enhancing formatting throughout the document. These improvements will help users better understand the framework’s features, installation instructions, and usage examples, ultimately enhancing their experience with AutoGen.