While exploring team collaboration, it was difficult to reorganize the teamwork as Outsystems does not support native integration with github.

It is possible to write your tool, but it delays development and requires a lot of resources.

It is necessary to implement a full direct and native integration of Outsystems version control and Github and to allow the user to use branching and pull request functionality.

create the possibility to connect my CSS via git, and thus be able to manage in all environments.

We have faced this issue several times where the Production version of the software is far behind the recent development. I know Outsystems suggests continuous deployment approach. But in real time scenario there are many cases we have seen, where we needed a master branch and local branch or current development branch. This concept is well known in SVN and git. We should think on it

agree

Not a new Idea, see 'Branching':
https://www.outsystems.com/ideas/160/branching/

This is already thought of/requested a long time ago (2010)

However, technically really challenging for the OutSystems team to implement.

It has already been tried out in an EAP, I don't know the internal status of this functionality other than that it is currently on 'Not right now'.

Hi @Jeroen Bindels 👨🏽‍🚀 

Thanks for your quick feedback.
My idea is similar to https://www.outsystems.com/ideas/160/branching/ , but the difference is about the use of specific technologies. These two are conventional technologies, and if we are going along with them then it could be easy to grasp and use their existing features.

nice thought ...!!!

I have tried to import a .css into outsystems with @import() and, besides it worked in browser, it did not work in outsystems' view.

So, I would like to suggest you any integration with github (or similiar) in order to allow us to use pre-processors, branchs in git, autoprefixer and so on. It would be a plugin like in trello, slack and others.

Thank you very much