[feature] Common replies to OpenWISP contributors

[nemesifier]

I find myself wasting a lot of time with recurring issues when issue comments or PRs, here's the most recurring problems and potential remediation actions.

The CI builds fails

• The bot could communicate this to the contributor by replying and mentioning the contributor in the comment
• The bot can provide a summary of the issues and potential remediations, eg:
  • If QA checks are failing due to code quality issues, it can explain how to run openwisp-qa-format and link to the contributing guidelines for reference
  • If QA checks are failing due to the commit message, it can propose a compliant commit message based on the commit message / PR title / issue title and description
  • If tests fail, it can copy the test failures in the comment description and link the CI build details.

A contributor comments "please assign this issue to me"

• The bot could quote the contributing guidelines where we say that they do not need to wait to be assigned to an issue to start working
• If the contributor opens a related PR, the bot could automatically assign the issue to them
• if the PR stalls and reviews are not addressed within 7 days, the bot could comment on the PR politely requesting to follow up with the review, after 14 days without review follow up it can declare the PR as stalled and unassign the issue automatically from the contributor

I am not sure what kind of solutions exist for these automations, but I have seen other orgs doing it and I think we should do more research.

[Piyushrathoree]

@pandafy can I work on this ? ETA : 3 days

[stktyagi]

@pandafy can I work on this ? ETA : 3 days

Hey @Piyushrathoree, As mentioned above you can submit a PR regarding any issue you find suitable. Make sure you read https://openwisp.io/docs/dev/developer/contributing.html

[nemesifier]

Before implementing this it could be good to have a minimal discussion on the implementation details, what approach do you want to use to solve this @Piyushrathoree?

[Piyushrathoree]

Before implementing this it could be good to have a minimal discussion on the implementation details, what approach do you want to use to solve this @Piyushrathoree?

@nemesifier hey Hi , yeah it will be good , so this issue can be solve by multiple ways , like adding automations tools (no code/low code implementation ) but what I'm suggesting here is to go with a simple yet really good way (according to a little research of mine used by Django org as well (used gpt for it )), and its to using a bot and using Github Actions for the CI builds fails as well as the basic comment thing. -- like as you described if anyone opens a PR, the issue will be assigned to the user by the bot. -- similarly with issues (code quality , commit message issuse and tests fail) it will notify the user with the description , and share any detail if needed to help the user.

[nemesifier]

@Piyushrathoree so you're suggesting to write a github actions for these tasks right? I am in favour of this approach so we can have full control but will also require a few iterations to get right. We are already using github actions, see: https://openwisp.io/docs/dev/utils/developer/reusable-github-utils.html

[Piyushrathoree]

yeah I see , what are you suggesting ? Iterations ?

[nemesifier]

@Piyushrathoree sorry I haven't understood very well your question. Yes, I am suggesting to iterate on it, draft something rough that works and refine it. Do you have any other doubt?