Animesh Kumar
Animesh Kumar
> > btw, have a look at the following PR which is of similar nature and was used to push Glee docs to website: > > > > * [ci:...
> @AnimeshKumar923 From what I understand the PR is setting up a workflow such that, on push to community docs in the `community` repo, we want the changes to sync...
also, what docs will we be pushing onto the website? @alequetzalli @TRohit20 I assume the `onboarding-guide` will definitely be pushed as far as I know... What else? Can we have...
> Question, @AnimeshKumar923, is this PR to replace the one I tried to make via #1064? I don't mind at all, if that is the case, I honestly still don't...
@alequetzalli _(DISCLAIMER: I'll try my best to explain, although I'm still learning so please verify the explanation @sambhavgupta0705 @akshatnema)_ # Automation Workflow - Whenever there's a docs PR on the...
> Thank you for that extremely detailed walk-through of your code, @AnimeshKumar923!! I really appreciate it. 😀 My pleasure! :grin: > > also, what docs will we be pushing onto...
> > NOTE: Sharing some notes that @KhudaDad414 shared with me via DM about this task in case it helps @AnimeshKumar923. > > If I understood the issue correctly then...
@sambhavgupta0705 I haven't added the [title and weight updating part](https://github.com/asyncapi/extensions-catalog/blob/7270922048f71b035d02d7dea950e642e2160dcc/.github/workflows/update-extensions-in-website.yml#L54C1-L69C15) of the workflow. I think we should specify which document should be displayed in which order. cc: @alequetzalli
> Yes you can remove that part I think The markdown updating part? I haven't added that to this file, so I guess that's excluded for now