Contributing
How to get a notebook displayed on the website
In the notebook metadata set the tags
and description
front_matter
properties. For example:
Note: Notebook metadata can be edited by opening the notebook in a text editor (Or "Open With..." -> "Text Editor" in VSCode)
The tags
field is a list of tags that will be used to categorize the notebook. The description
field is a brief description of the notebook.
Best practices for authoring notebooks
The following points are best practices for authoring notebooks to ensure consistency and ease of use for the website.
The Colab button will be automatically generated on the website for all notebooks where it is missing. Going forward, it is recommended to not include the Colab button in the notebook itself.
Ensure the header is a
h1
header, -#
Don't put anything between the yaml and the header
Consistency for installation and LLM config
You don't need to explain in depth how to install AutoGen. Unless there are specific instructions for the notebook just use the following markdown snippet:
Or if extras are needed:
When specifying the config list, to ensure consistency it is best to use approximately the following code:
Then after the code cell where this is used, include the following markdown snippet:
Testing
Notebooks can be tested by running:
This will automatically scan for all notebooks in the notebook/ and website/ dirs.
To test a specific notebook pass its path:
Options:
--timeout
- timeout for a single notebook--exit-on-first-fail
- stop executing further notebooks after the first one fails
Skip tests
If a notebook needs to be skipped then add to the notebook metadata:
Metadata fields
All possible metadata fields are as follows:
Last updated