Skip to content
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

Automatic tagging and assigning of Pull Requests and Issues #65

Open
czgdp1807 opened this issue Apr 27, 2019 · 4 comments
Open

Automatic tagging and assigning of Pull Requests and Issues #65

czgdp1807 opened this issue Apr 27, 2019 · 4 comments

Comments

@czgdp1807
Copy link
Member

czgdp1807 commented Apr 27, 2019

I don't know if this is feasible, however, I would still like the sympy-bot to tag the PRs with labels, at least related to the module mentioned in the release notes. This would help the new contributors to help in improving sympy by finding the PRs and Issues of the module that interests them.
In addition it would be great to automatically assign an issue to someone by using commands like, Ping, etc.
This will also reduce a lot of work load on members of the organization.
P.S. - I observed that zulip-bot is capable of doing the above.

@czgdp1807 czgdp1807 changed the title Automatic tagging of Pull Requests and Issues Automatic tagging and assigning of Pull Requests and Issues Apr 27, 2019
@asmeurer
Copy link
Member

Adding a tag based on the release notes modules would be easy. Beyond that, how would it know what labels to add to an issue or pull request?

@czgdp1807
Copy link
Member Author

One way can be to check which module's code is changed, may be, by checking the diff on github. Is that possible?

@asmeurer
Copy link
Member

Yes, though that likely won't give more information than the release notes entry for most pull requests.

@czgdp1807
Copy link
Member Author

Yes, but that will be definite as compared to release notes entries, which are sometimes wrong, especially with new contributors.
Moreover, if possible, we can analyse the diff in a more detailed manner, like the affected class will give more information. I am unable to figure out how zulip-bot is able to tag PRs so intelligently.
For the time being, we can go with module changes/release notes for labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants