github-actions not friendly, commenting twice

[nicolas-raoul]

There are several issues seen in the screenshot below (if you submit a pull request for the present issue feel free to only address one of the bullets):

• [major] github-actions not friendly at all. Should rather say Thank you for your interest! This issue has already been assigned, but you can find another issue to work on at https://github.com/commons-app/apps-android-commons/issues?q=is%3Aissue%20state%3Aopen%20type%3ABug%20no%3Aassignee%20-label%3A%22low%20priority%22%20-label%3Adebated%20-label%3Aupstream By the way, welcome to the team! Please make sure to read [...] (it was priyanshudotexe's first ever contact with us). (other issue were that happened)
• [major] Commented again a second time, that was unnecessary and will confuse newcomers.
• [minor] Ideally Copilot could have understood that reassigning was OK in this case, because the assignee had written I’m afraid I’m not able to solve this issue at the moment. It might be better if someone else could take a look. Or maybe Copilot could have understood that a categorical refusal was not ideal.

[RitikaPahwa4444]

Sorry about this! I'm disabling it for some time as it's adding comments even when we're not asking for an issue to be assigned to us.

[major] Some contributors raise a PR without asking to be assigned. Now if someone asks to be assigned, this action ends up assigning the task to them. Not a good situation to be in, especially if the one asking is new, they'll end up doing the work that has already been done. We need to check for active PRs (< 1 month old) before assigning.

All of this happened here: #6551 (comment). The assignee is new, so I'd to suggest them to review the PR or take a reference instead of putting in all the effort.

[nicolas-raoul]

All of this happened here: #6551

My understanding is that we were just playing around with Copilot, and I was completely ready to give the issue to anyone who might want it. Actually copilot was unassigned. :-)

We need to check for active PRs (< 1 month old) before assigning

Checking this would had more work on the core developers. I would argue that this check is not necessary, anyone submitting a PR should be assigned to the issue. In other words, someone writing a PR without getting the issue assigned should not expect anything.

What do you think? :-)

[RitikaPahwa4444]

Actually copilot was unassigned. :-)

Yes, but I do expect some contributors to follow this kind of a flow, so I thought it was worth mentioning 😅

In other words, someone writing a PR without getting the issue assigned should not expect anything.

This depends on the community. It's completely normal to send a PR without asking for an issue to be assigned in many communities, and those contributors tend to carry that behaviour forward. Some contributors don't even raise an issue and send improvements. No doubt this gets complex and we can simply make it a rule to ask before raising a PR :)