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
Is your feature request related to a problem? Please describe. @zulipbot is a GitHub workflow bot application for the Zulip organization and its repositories. Written in Node.js, the bot manages issues and pull requests in the repository in order to create a better workflow for Zulip contributors.
zulipbot's purpose is to work around various limitations in GitHub’s binary permissions and notifications systems to create a better workflow for our contributors. It allows anyone to perform issue triage (self-assigning and labeling issues), not just the core contributors trusted with full write access to the repository (which is the only model GitHub supports). Additionally, zulipbot monitors the activity of issues and pull requests, notifying contributors about new merge conflicts, continuous integration build results, inactivity, and more.
Describe the solution you'd like
We can install Zulipbot to our organization repositories by following this installation guide here. This will allow issues to get assigned to whoever comments first and also unassigned if there is inactivity for a given period of time reducing the work for maintainers.
I like the idea. I am not totally clear yet how it will work but I will learn when we test it on the about-moja-global repository. After that we can roll it out to the other repos. Good idea. Thank you. Keep those ideas coming!!
@Tlazypanda Thanks for the idea. It is great. Can we also create the add Project-bot to manage and optimize the Kanban board? Is that the Project- Bot best practice for board?
Patamap
changed the title
Add Zulipbot to manage and optimize Github Workflow
EPIC for Add Zulipbot to manage and optimize Github Workflow
Jun 22, 2020
@Tlazypanda, can you update the specification of Zulipbot feature, please?
The requirements in the issue itself are
The issue creator can assign the issue to him/herself with type "@name claim"
The issue creator can unassign the issue from him/herself with type "@name abandon"
The new creator can only chose the issue with label with type "@name newcomer"
If the contributor does the pull request that is conflicted to the existing one, then error msg "......." will send the email to remind twice within 10 days.
@Patamap@gmajan So the zulipbot setup has been done and this can be closed. Moving to #63 to discuss more on contribution guidelines specific for zulipbot to be added to the readme so that contributors know what commands to write to claim issues and/or add labels. Thanks ✌️
Is your feature request related to a problem? Please describe.
@zulipbot is a GitHub workflow bot application for the Zulip organization and its repositories. Written in Node.js, the bot manages issues and pull requests in the repository in order to create a better workflow for Zulip contributors.
zulipbot's purpose is to work around various limitations in GitHub’s binary permissions and notifications systems to create a better workflow for our contributors. It allows anyone to perform issue triage (self-assigning and labeling issues), not just the core contributors trusted with full write access to the repository (which is the only model GitHub supports). Additionally, zulipbot monitors the activity of issues and pull requests, notifying contributors about new merge conflicts, continuous integration build results, inactivity, and more.
Describe the solution you'd like
We can install Zulipbot to our organization repositories by following this installation guide here. This will allow issues to get assigned to whoever comments first and also unassigned if there is inactivity for a given period of time reducing the work for maintainers.
See the instruction here: https://docs.google.com/document/d/1B1k2kRpAdtl9U8v-ze-uO56m8rldIuiAG1nQoZRpyDI/edit
Additional context
Screenshots showing the bot in action: -
The text was updated successfully, but these errors were encountered: