ci: use latest action to replicate workflows to other repos

[derberg]

Description

• use new version of action that copies files from this repo to other repos. It now supports not only workflow files
• this change do not handle cleanup. Cleanup like removal go-related workflows from node project, or nodejs-related workflows from go projects is a manual work that has to be done by owners of related repositories when they have time. This action and workflow do not detect files that are no longer needed and therefor should be removed from some repo.
• I don't think we should replicate other files than contributing guide and code of conduct. Imho support and other files can stay here as they are anyway supported by GitHub properly

TODO:

• before it is merged I need to make sure CONTRIBUTING.md is only different for spec and community. Maybe other repos have their own versions
• before it is merged I need to add proper topics to Go and NodeJS projects

Related issue(s)
Resolves #39
Resolves #40

@jonaslagoni pinging you as you are the owner of related issues
@smoya pinging you as you are owner of go projects
@KhudaDad414 pinging you for obvious reasons - I need your review
@magicmatatjahu pinging you so you know we can also have docker only workflows distributed only to repost with docker topic. Also new action also supports branches option, so we can do replication of files in branches different than main, in case we want.

[KhudaDad414]

Thanks, @derberg 🙇. love the new name of the action :)

[KhudaDad414]

@HarshCasper you may be interested in this PR as well, for #147

[derberg]

@magicmatatjahu @jonaslagoni I went through all repos that have their own contributing guide. Some of them I ignore in new workflows. I need your opinion on what about:

• https://github.com/asyncapi/asyncapi-react/blob/master/CONTRIBUTING.md
• https://github.com/asyncapi/modelina/blob/master/docs/contributing.md
• https://github.com/asyncapi/dotnet-nats-template/blob/master/CONTRIBUTING.md
• https://github.com/asyncapi/ts-nats-template/blob/master/CONTRIBUTING.md

my suggestion is to take "custom" parts into README.md into Development section, or Contributing section + switch to generic CONTRIBUTING.md

[magicmatatjahu]

@derberg To correctly understand: do we need to remove our custom contribution guide and link to the CONTRIBUTING.md which will be copied to the every repo by "global" workflow or should this link point to a contribution in the community repo?

EDIT: Ok, I see we're going to have the CONTRIBUTING.md in every repo.

[derberg]

@magicmatatjahu you can have your custom CONTRIBUTING guide as you have now, but you can also have the one that we will copy over. Up to you. You will just need to move "custom" parts somewhere so they are not lost

[smoya]

topics_to_include is key. This is awesome. This is amazing 🥇 💯 👏

[smoya]

@derberg I added the golang topic into all go repositories that didn't have it.
Additionally, also added nodejs topic to https://github.com/asyncapi/server-api (I'm owner).

[quetzalliwrites]

Just 2 tiny items 🎉🎉🎉

[quetzalliwrites]

🚢 🚢 🚢

[derberg]

@magicmatatjahu @jonaslagoni so what is your take on mentioned CONTRIBUTING guides? should I add them to ignored for now?

[jonaslagoni]

@magicmatatjahu @jonaslagoni so what is your take on mentioned CONTRIBUTING guides? should I add them to ignored for now?

Sounds good 👍

[derberg]

@magicmatatjahu pingy pongy

[magicmatatjahu]

@derberg Sorry, I missed that notification. You can go ahead, as I see with react-component won't be problem.

[derberg]

all adjusted as requested
we also have nodejs topic added where needed, same with go thanks to @smoya

I need just one 🍏

[smoya]

🚀 🌔

[magicmatatjahu]

LGTM!

[KhudaDad414]

LGTM!

[derberg]

/rtm