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?

need to look into it

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.

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

Hi @anshgoyalevil , i would like to take this up

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

@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.

Bounty Issue's Timeline

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.

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

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

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 (githubID 81870866), please provide an update to the PR.