You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+20-20
Original file line number
Diff line number
Diff line change
@@ -49,8 +49,8 @@ We will update verion numbers according to the following rules:
49
49
50
50
1. Create a PR that updates the version numbers across the codebase ([example](https://github.com/microsoft/autogen/pull/4359))
51
51
2. The docs CI will fail for the PR, but this is expected and will be resolved in the next step
52
-
2. After merging the PR, create and push a tag that corresponds to the new verion. For example, for `0.4.0.dev7`:
53
-
-`git tag 0.4.0.dev7 && git push origin 0.4.0.dev7`
52
+
2. After merging the PR, create and push a tag that corresponds to the new verion. For example, for `0.4.0.dev8`:
53
+
-`git tag 0.4.0.dev8 && git push origin 0.4.0.dev8`
54
54
3. Restart the docs CI by finding the failed [job corresponding to the `push` event](https://github.com/microsoft/autogen/actions/workflows/docs.yml) and restarting all jobs
55
55
4. Run [this](https://github.com/microsoft/autogen/actions/workflows/single-python-package.yml) workflow for each of the packages that need to be released and get an approval for the release for it to run
56
56
@@ -59,27 +59,27 @@ We will update verion numbers according to the following rules:
59
59
To help ensure the health of the project and community the AutoGen committers have a weekly triage process to ensure that all issues and pull requests are reviewed and addressed in a timely manner. The following documents the responsibilites while on triage duty:
60
60
61
61
- Issues
62
-
- Review all new issues - these will be tagged with [`needs-triage`](https://github.com/microsoft/autogen/issues?q=is%3Aissue%20state%3Aopen%20label%3Aneeds-triage).
63
-
- Apply appropriate labels:
64
-
- One of `proj-*` labels based on the project the issue is related to
65
-
-`documentation`: related to documentation
66
-
-`x-lang`: related to cross language functionality
67
-
-`dotnet`: related to .NET
68
-
- Add the issue to a relevant milestone if necessary
69
-
- If you can resolve the issue or reply to the OP please do.
70
-
- If you cannot resolve the issue, assign it to the appropriate person.
71
-
- If awaiting a reply add the tag `awaiting-op-response` (this will be auto removed when the OP replies).
72
-
- Bonus: there is a backlog of old issues that need to be reviewed - if you have time, review these as well and close or refresh as many as you can.
62
+
- Review all new issues - these will be tagged with [`needs-triage`](https://github.com/microsoft/autogen/issues?q=is%3Aissue%20state%3Aopen%20label%3Aneeds-triage).
63
+
- Apply appropriate labels:
64
+
- One of `proj-*` labels based on the project the issue is related to
65
+
-`documentation`: related to documentation
66
+
-`x-lang`: related to cross language functionality
67
+
-`dotnet`: related to .NET
68
+
- Add the issue to a relevant milestone if necessary
69
+
- If you can resolve the issue or reply to the OP please do.
70
+
- If you cannot resolve the issue, assign it to the appropriate person.
71
+
- If awaiting a reply add the tag `awaiting-op-response` (this will be auto removed when the OP replies).
72
+
- Bonus: there is a backlog of old issues that need to be reviewed - if you have time, review these as well and close or refresh as many as you can.
73
73
- PRs
74
-
- The UX on GH flags all recently updated PRs. Draft PRs can be ignored, otherwise review all recently updated PRs.
75
-
- If a PR is ready for review and you can provide one please go ahead. If you cant, please assign someone. You can quickly spin up a codespace with the PR to test it out.
76
-
- If a PR is needing a reply from the op, please tag it `awaiting-op-response`.
77
-
- If a PR is approved and passes CI, its ready to merge, please do so.
78
-
- If it looks like there is a possibly transient CI failure, re-run failed jobs.
74
+
- The UX on GH flags all recently updated PRs. Draft PRs can be ignored, otherwise review all recently updated PRs.
75
+
- If a PR is ready for review and you can provide one please go ahead. If you cant, please assign someone. You can quickly spin up a codespace with the PR to test it out.
76
+
- If a PR is needing a reply from the op, please tag it `awaiting-op-response`.
77
+
- If a PR is approved and passes CI, its ready to merge, please do so.
78
+
- If it looks like there is a possibly transient CI failure, re-run failed jobs.
79
79
- Discussions
80
-
- Look for recently updated discussions and reply as needed or find someone on the team to reply.
80
+
- Look for recently updated discussions and reply as needed or find someone on the team to reply.
81
81
- Security
82
-
- Look through any securty alerts and file issues or dismiss as needed.
82
+
- Look through any securty alerts and file issues or dismiss as needed.
> - (11/14/24) ⚠️ In response to a number of asks to clarify and distinguish between official AutoGen and its forks that created confusion, we issued a [clarification statement](https://github.com/microsoft/autogen/discussions/4217).
16
16
> - (10/13/24) Interested in the standard AutoGen as a prior user? Find it at the actively-maintained *AutoGen*[0.2 branch](https://github.com/microsoft/autogen/tree/0.2) and `autogen-agentchat~=0.2` PyPi package.
17
17
> - (10/02/24) [AutoGen 0.4](https://microsoft.github.io/autogen/dev) is a from-the-ground-up rewrite of AutoGen. Learn more about the history, goals and future at [this blog post](https://microsoft.github.io/autogen/blog). We’re excited to work with the community to gather feedback, refine, and improve the project before we officially release 0.4. This is a big change, so AutoGen 0.2 is still available, maintained, and developed in the [0.2 branch](https://github.com/microsoft/autogen/tree/0.2).
@@ -104,7 +104,7 @@ We look forward to your contributions!
During development, you may need to test changes made to any of the packages.\
25
27
To do so, create a virtual environment where the AutoGen packages are installed based on the current state of the directory.\
26
28
Run the following commands at the root level of the Python directory:
@@ -29,11 +31,14 @@ Run the following commands at the root level of the Python directory:
29
31
uv sync --all-extras
30
32
source .venv/bin/activate
31
33
```
34
+
32
35
-`uv sync --all-extras` will create a `.venv` directory at the current level and install packages from the current directory along with any other dependencies. The `all-extras` flag adds optional dependencies.
33
36
-`source .venv/bin/activate` activates the virtual environment.
34
37
35
38
### Common Tasks
39
+
36
40
To create a pull request (PR), ensure the following checks are met. You can run each check individually:
0 commit comments