Feature: Manual assigning label "📍 Assigned" should trigger posting a comment and assign last commenter

[koppor]

Type of feature

💡 Feature

Current behavior

Currently, the label "📍 Assigned" is assigned after a command. Soemtimes, there is manual assignment necessary, which is currently not covered by the action.

Suggested solution

When someone is assigned AND the label "📍 Assigned" was assigned, the action should post the welcoming text.

I know, this is also possible by other actions (e.g., Create or Update Comment), but it would be nice to have an all-in-one solution.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[koppor]

I think, we just need to add the number-of-days to our text in our action. https://github.com/JabRef/jabref/blob/ec2059af58dc7b7793e9f6e0bafc8711140cd2d7/.github/workflows/on-labeled-issue.yml#L15. This is good enough and reduces handling of special cases (e.g., if the text is already there, it should not be posted...)

[koppor]

Update: On GitHub mobile it is easier to add a label than to add text. Thus, the wish changes to: Assign the last commenter and post text on label creation 😅

[koppor]

This is important if a maintaimer does not want to be notified of the issue at all. When commenting, the user is notified on each change of the issue. They need to unsubscribe. With the label approach no additional actions by the user are necessary!

[takanome-dev]

When someone is assigned AND the label "📍 Assigned" was assigned, the action should post the welcoming text.

I agree with this approach!

the wish changes to: Assign the last commenter and post text on label creation 😅
This is important if a maintainer does not want to be notified of the issue at all. When commenting, the user is notified on each change of the issue. They need to unsubscribe. With the label approach no additional actions by the user are necessary!

I'm not entirely sure I understand this part. Could you clarify what you mean by "assign the last commenter and post text on label creation" and how the label approach helps in avoiding notifications? I'd love to get more context!

[koppor]

I'm not entirely sure I understand this part. Could you clarify what you mean by "assign the last commenter and post text on label creation" and how the label approach helps in avoiding notifications? I'd love to get more context!

Example: After the comment JabRef/jabref#4257 (comment) Thilo assigned FirstTimeContribution.This triggers GitHub to post a text. Since it was not Thilo himself, he does not get notifications, because he is not “involved“ in the conversation!

[takanome-dev]

Got it, will look into it 👍