-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add automation to push bindings docs to website #251
Comments
hey @derberg we need similar workflow like this one(https://github.com/asyncapi/extensions-catalog/blob/master/.github/workflows/update-extensions-in-website.yml ) but to be adapted for binding |
@ibishal exactly, added it to bounty |
@derberg I wish to work on this issue, under the Bounty program. |
Bounty Issue's service commentText labels: @asyncapi/bounty_team The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.Third-party contributors should coherently articulate how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue. |
@akshatnema really? nice ❤️ I assign to @akshatnema that is a maintainer in AsyncAPI org, a maintainer in website. This automation is actually also website related as the automation will be pushing markdown files to website. So not much onboarding is needed |
Really? But I do have certain questions with me 😅 . What are the files you need to show them in the website? Like I don't see any |
@akshatnema please check extensions catalog repo, there is no docs either. Get familiar with what automation does there |
I noticed I forgot that I was suppose to wait 3 days before I publish a decision who will work on issues. I don't have a better excuse other than "Monday". My apologies. |
Yeah, I looked in its implementations, but as per the current wdyt? @derberg |
One of the suggestions could be to change the name of |
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. |
@akshatnema the automation can do whatever is needed to make it work in website. Automation can definitely rename |
Hey @aeworxet, |
Upon request of the Bounty Program Participant (@akshatnema), all remaining target dates of the Bounty Issue's Timeline are extended by two 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. |
I'm anyway also not available starting from this Friday to next Wednesday - short holidays. So won't be able to review that time |
@akshatnema, please provide an update to the PR. |
1 similar comment
@akshatnema, please provide an update to the PR. |
@akshatnema had scheduled a call with @derberg on 2024-08-27 to clarify some final details on this Bounty Issue before merging #258. |
Response, critical for technical resolution of this Bounty Issue (clarification on implementation) was delayed for one period of three consecutive working days so all remaining target dates of the Bounty Issue's Timeline are extended by two 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. |
Development was delayed by one day due to an emergency situation. |
Due to a little emergency at the Bounty Program Participant's side (@akshatnema), all remaining target dates of the Bounty Issue's Timeline are extended by one calendar week. 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. |
@akshatnema did all that was needed there are issues but not related to his work but because of #261 (comment) that once solved/reverted the automation will work like a charm |
Bounty Issue Is Completed 🎉@akshatnema, please go to the AsyncAPI page on Open Collective and submit an invoice for |
under https://asyncapi.com/docs/reference/ we have specification rendered and also now extensions
We just need to add workflow like https://github.com/asyncapi/extensions-catalog/blob/master/.github/workflows/update-extensions-in-website.yml to copy over markdown files with proper names and render in website
It's not important only for visibility and discoverability of info (navingate from one place and search integration) but also all keywords used in bindings increase SEO position for asyncapi.com
The text was updated successfully, but these errors were encountered: