Typebot
Log in

Share feedback, ideas and get community help

Updated 6 months ago

Correct way to upload a block to official git

At a glance

The community member has developed an integration between their CRM and Typebot (for lead creation and updating), and they would like to make it available to the public. They are unsure about the process, specifically what to include in the issue they need to open, where to put their code for evaluation, and whether they should do a PR first.

The comments suggest that the community member should create an issue before implementing the block, so that the implementation can be checked. However, since the block is already created, the community member can create a PR with a good description of the block. The comments also note that there is no guarantee the PR will be officially merged, and that creating an issue before is always a good idea to avoid unnecessary work.

WWellington Capoia
Hello, I have a CRM and I ended up developing an integration between it and typebot (lead creation and updating), and I would like to make it available to the public.
Reading the documentation it says to open an issue first, to check if everything is correct, but I don't know exactly what I need to put in this issue, and I'm afraid of opening it wrong.

What do I need to inform in the issue? Where do I put my code for evaluation? Do I do PR first?
B
2 comments
BBaptiste
The issue in theory should be created prior to the block implementation so that we can make sure you implement it correctly etc. But since you have the block already created, you can just create a PR with a good description of what the block is about
BBaptiste
But I don’t guarantee that it will be officially merge! Creating an issue before is always a good thing to avoid unecessary work
Add a reply
Sign up and join the conversation on Discord