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

EPIC for Add Zulipbot to manage and optimize Github Workflow #45

Closed
Tlazypanda opened this issue Jun 11, 2020 · 4 comments
Closed

EPIC for Add Zulipbot to manage and optimize Github Workflow #45

Tlazypanda opened this issue Jun 11, 2020 · 4 comments
Assignees
Labels
Feature request Suggest an idea for this project

Comments

@Tlazypanda
Copy link
Collaborator

Tlazypanda commented Jun 11, 2020

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: -
image

image

@Tlazypanda Tlazypanda added the Feature request Suggest an idea for this project label Jun 11, 2020
@Tlazypanda Tlazypanda added this to the Technical Onboarding 2020 milestone Jun 11, 2020
@gmajan
Copy link
Member

gmajan commented Jun 11, 2020

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!!

@Patamap
Copy link
Contributor

Patamap commented Jun 15, 2020

@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 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
@Patamap
Copy link
Contributor

Patamap commented Jun 29, 2020

@Tlazypanda, can you update the specification of Zulipbot feature, please?

The requirements in the issue itself are

  1. The issue creator can assign the issue to him/herself with type "@name claim"
  2. The issue creator can unassign the issue from him/herself with type "@name abandon"
  3. The new creator can only chose the issue with label with type "@name newcomer"
  4. 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.

@Tlazypanda
Copy link
Collaborator Author

@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 ✌️

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

No branches or pull requests

4 participants