Perfect workflow for notifying triagers

[sambhavgupta0705]

Why do we need this improvement?

Currently the workflow for notifying triage maintainers of code and doc is not working properly for which we need to setup a perfect workflow to notify triage maintainers

How will this change help?

It will help us in maintaining the code review architecture in a better way

How could it be implemented/designed?

Need to setup a workflow for this

[JeelRajodiya]

Hello, I looked up the logs of the notify-triager workflow. Is this error relevant to the issue? or we have some other issue with the workflow?

[sambhavgupta0705]

need to look into it

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q4, bounty/medium, bounty/coding
First assignment to regular contributors: 2024-09-20 00:00:00 UTC+12:00
End Of Life after: 2024-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[aialok]

Hi team,

I would like to take on this issue. I have good experience with GitHub Actions from my GSoC work, where I built the CI/CD pipeline for the JSON Schema website.

Thank you! : )

[Gmin2]

Hi @anshgoyalevil , i would like to take this up

[sambhavgupta0705]

@aeworxet I would like to work on this issue under bounty program

[aeworxet]

@sambhavgupta0705 is an AsyncAPI Maintainer specified in https://raw.githubusercontent.com/asyncapi/community/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2024-09-17	2024-10-07	2024-11-17	2024-10-20	2024-11-03	2024-11-17

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[sambhavgupta0705]

Hey!!
I am a bit occupied with my academics for this month so would like to extend this issue by 4 weeks

[aeworxet]

Upon request of the Bounty Program Participant (@sambhavgupta0705, githubID 81870866), all remaining target dates of the Bounty Issue's Timeline are extended by four calendar weeks.

Bounty Issue's Timeline Extended

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2024-09-17	2024-10-07	2024-12-15	2024-11-17	2024-12-01	2024-12-15

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[aeworxet]

@sambhavgupta0705 (githubID 81870866), please provide an update to the PR.

[aeworxet]

@sambhavgupta0705 (githubID 81870866), please provide an update to the PR.