# Feature branches and source control? **URL:** \ **Category:** Ask us anything\ **Created:** [August 21, 2023, 6:25pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961 "2023-08-21T18:25:40Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![AJAW](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@AJAW](https://community.weweb.io/u/AJAW)\ **Post date:** [August 21, 2023, 6:25pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/1 "2023-08-21T18:25:40Z")
Hey, I own an agency and we specialize in creating weweb apps. First of all, we all love weweb and its an amazing tool! Although, one of the annoying aspects is working with multiple devs on the same project. We have a QA person that tests all of the completed tickets on our staging environment. What happens sometimes is, one dev finishes something and is ready to publish his changes, whereas the other is in progress. This creates a problem where the staging environment might have changes from multiple developers at a time, not all being fully completed and some causing bugs/preventing testing. We of course can mitigate this issue with proper communication, but ideally we could create ‘feature branches’ for each ticket and merge them up the chain separately. Is something like this possible/on the roadmap in the near future? Best regards, Axel. ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [August 24, 2023, 9:36pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/2 "2023-08-24T21:36:42Z")
Hi @AJAW 👋 Great question! It’s something the product team is thinking a lot about these days. They are currently exploring different options to handle the versioning of components and design systems which they expect will do a lot of the heavy lifting. Can’t yet communicate an ETA because there are a couple of UX design challenges they want to nail before starting development work. ---
**Author:** ![AJAW](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@AJAW](https://community.weweb.io/u/AJAW)\ **Post date:** [August 24, 2023, 11:39pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/3 "2023-08-24T23:39:31Z")
Awesome! Looking forward to that 🙂 ---
**Author:** ![liam\_putra](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/liam_putra/32/1057_2.png) [@liam\_putra](https://community.weweb.io/u/liam_putra)\ **Post date:** [September 20, 2023, 3:48am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/4 "2023-09-20T03:48:48Z")
any update on this joyce ? this is super important feature. flutterflow 4.0 just launched and they have git branches for features. you might want to take a look at that ---
**Author:** ![flo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/flo/32/13260_2.png) [@flo](https://community.weweb.io/u/flo)\ **Post date:** [September 22, 2023, 5:13pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/5 "2023-09-22T17:13:51Z")
Hi @AJAW and @liam_putra , As Joyce mentioned, this is something we are working on. Here’s a preview of what’s coming: 1. **Project Versioning and Rollback** 2. **Revamping Design System with Version Control** 3. **Components with Version Control** We believe that these version control features are the initial steps toward branching. They are essential for effectively scoping collaborators’ work and ensuring maintainability and scalability. These measures will minimize conflicts when merging potential branches, which is a significant challenge when dealing with branching, especially in a no-code environment where you can’t simply update a single line of code. You have to decide who wins. Our plan is to release project version control and design system revamping in October, followed by components in November. Branching will be introduced later in 2024 after we have refined our version control capabilities sufficiently. Hope this helps! Feel free to comment. ---
**Author:** ![AJAW](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@AJAW](https://community.weweb.io/u/AJAW)\ **Post date:** [September 22, 2023, 5:23pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/6 "2023-09-22T17:23:35Z")
Hey @flo, thank you for answering! Very excited about the upcoming features, cant wait! Once we have components, versioning and all that I think weweb will be the greatest no-code tool on the market by a big margin (in my book it already is due to the customizability aspect) I will be happy to participate in a beta with our agency www.natural.agency for any of the features ---
**Author:** ![liam\_putra](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/liam_putra/32/1057_2.png) [@liam\_putra](https://community.weweb.io/u/liam_putra)\ **Post date:** [September 24, 2023, 4:03am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/7 "2023-09-24T04:03:10Z")
Looking forward to these updates!! ---
**Author:** ![gbeaudoin](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/gbeaudoin/32/3221_2.png) [@gbeaudoin](https://community.weweb.io/u/gbeaudoin)\ **Post date:** [February 21, 2024, 1:34pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/8 "2024-02-21T13:34:21Z")
> [@flo](#): > > Branching will be introduced later in 2024 after we have refined our version control capabilities sufficiently. Hi Flo, really excited for this to happen! Just wondering if you have a status update on it at this time. Thanks 🙂 ---
**Author:** ![viktor.kyrychenko](https://avatars.discourse-cdn.com/v4/letter/v/c67d28/32.png) [@viktor.kyrychenko](https://community.weweb.io/u/viktor.kyrychenko)\ **Post date:** [February 28, 2024, 9:27am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/9 "2024-02-28T09:27:36Z")
@flo @Joyce any updates on when we can expect new features for version control? 😇 ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [February 28, 2024, 10:56am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/10 "2024-02-28T10:56:07Z")
Not yet 🙂 The priorities for Q2 are being defined as we speak 😄 ![CleanShot 2024-02-28 at 11.55.04](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/b/b5e20363345dd3023d43b0b93b7452d09bc92da0.gif) The suspense is killing me too! 🤣 ---
**Author:** ![viktor.kyrychenko](https://avatars.discourse-cdn.com/v4/letter/v/c67d28/32.png) [@viktor.kyrychenko](https://community.weweb.io/u/viktor.kyrychenko)\ **Post date:** [February 28, 2024, 11:14am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/11 "2024-02-28T11:14:42Z")
ahaha)) looking forward to the announcement 🙂 P.S. How do you like gather.town? 🙂 ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [February 28, 2024, 11:46am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/12 "2024-02-28T11:46:31Z")
> [@viktor.kyrychenko](#): > > P.S. How do you like gather.town? 🙂 I really like it! It makes remote work much more fun ---
**Author:** ![viktor.kyrychenko](https://avatars.discourse-cdn.com/v4/letter/v/c67d28/32.png) [@viktor.kyrychenko](https://community.weweb.io/u/viktor.kyrychenko)\ **Post date:** [November 8, 2024, 8:45am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/13 "2024-11-08T08:45:30Z")
Hi Flo, I wonder what the status with Version Control updates is? It’s been a while. We are waiting for it very much, because it actually would make the collaborative work of several developers on one project way more easier (right now it’s really stressful when it comes to control of changes). ---
**Author:** ![ben](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/ben/32/5605_2.png) [@ben](https://community.weweb.io/u/ben)\ **Post date:** [November 8, 2024, 10:31am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/14 "2024-11-08T10:31:47Z")
Very much confronted with the same challenges atm. Looking forward to releases on this. ---
**Author:** ![tomlouwagie](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@tomlouwagie](https://community.weweb.io/u/tomlouwagie)\ **Post date:** [November 15, 2024, 9:27am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/15 "2024-11-15T09:27:08Z")
Hi @flo is there any update on when this released? I run a Bubble agency and the main thing preventing us from using WeWeb is that we do not have branches, this is important when working with a production app or with several developers. ---
**Author:** ![allison](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@allison](https://community.weweb.io/u/allison)\ **Post date:** [December 10, 2024, 6:34pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/16 "2024-12-10T18:34:38Z")
Hi, Any status update on source control / branching feature release? Thank you! ---
**Author:** ![carrano\_dot\_dev](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/carrano_dot_dev/32/10547_2.png) [@carrano\_dot\_dev](https://community.weweb.io/u/carrano_dot_dev)\ **Post date:** [December 10, 2024, 10:03pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/17 "2024-12-10T22:03:19Z")
Apparently they’re focusing on AI features at the moment. I understand why they’re doing it from a marketing perspective, but dang, there are so many other more important and useful features to implement. Features like this. ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [December 11, 2024, 7:27am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/19 "2024-12-11T07:27:28Z")
I think you’re as delusional as the others if you have this narrow AI being the only thing that makes a company stay afloat mentality. Welcome to the community, try to not be a dick. Why the hell are you even in a no-code tool’s community talking shit if no-code is obsolete? It could be a sad time for WeWeb if the AI update brings toxic people like you @sproutsdev ---
**Author:** ![ben](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/ben/32/5605_2.png) [@ben](https://community.weweb.io/u/ben)\ **Post date:** [December 11, 2024, 7:35am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/20 "2024-12-11T07:35:35Z")
100% with @Broberto. @allison’s follow-up question is a very valid one. As I understand this is on the roadmap of 2025. @carrano_dot_dev AI is “hot” - but there is true power to it. Something to be leveraged on features in the sphere of collaboration (such as branching). ---
**Author:** ![carrano\_dot\_dev](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/carrano_dot_dev/32/10547_2.png) [@carrano\_dot\_dev](https://community.weweb.io/u/carrano_dot_dev)\ **Post date:** [December 11, 2024, 10:42am UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/21 "2024-12-11T10:42:35Z")
I’m definitely not saying AI isn’t powerful/useful. I use it everyday and I use Chatgpt in conjunction with Weweb for things like writing scripts and brainstorming architecture. I even studied it well before all this LLM craze. I just think that at the current state of AI, a more involved integration with Weweb won’t have a very profound effect from a dev perspective. I’d imagine it would mostly help beginners. Additionally, if AI gets to the point where it is useful for experienced devs using Weweb, devs and Weweb alike could face obsolescence. Under those circumstances, any effort put into tighter integration might prove futile in the long run. [Next page](https://community.weweb.io/t/feature-branches-and-source-control/3961.md?page=2)