Interesting! I have seen this at one company I worked at. We were trying to put all changes to the database in git. Main and develop always got out of sync though as we weren’t deploying from the code in source control.
We use github flow, and it's sooo good compared to other teams using gitflow. We're much faster rolling out changes to prod, and since we have unit + integration tests running on our branch pipelines, we're normally sure the branch is safe to be merged to master
We do GitHub flow and we publish with each commit to main (creating a docker image), but we only automatically deploy to a dev environment. Production deployment is done by hand, and not every version number is deployed there.
Dude, you nailed it! Great content. I request more Git goodies ... Not sure if this is in your wheelhouse, but if it is, help us all become Git masters. There is a lot of content out there, but there are also a ton of gaps past the beginner and intermediate levels. Good luck w/ the channel! Subscribed
But you didn’t talk about the difference between a version and a release, because you could create a new version without creating a release, can you give an explanation about this case please ? Thank you
My previous state owned company introduced scrum but teams weren't cooperative and nobody used Git properly, so the new scrum master was always bouncing from team leader to team leader asking for progress 😂
Actually i had doubt Aex , does the source control branches remains same regradless of the platform , suppose lets say we have 5 branches in Git , will the same be present in bitbucket and other platforms Thanks in advance!
Yes they work across platform as they are just a function of git. It is possible to mirror repositories from GitHub to Bitbucket but I haven’t done it myself before.
It depends on the company but places I have worked great them as the following: DEV: Every commit to develop gets deployed here. Can be unstable mainly used for developer testing. SANDBOX: I worked in payments so the sandbox environment was also open to the public to use for testing. We treated this as a pre production environment and only production ready releases went here.
I think eventually we'll just discard all the agile/ scrum/ sprint nonsense and base development around git or github practises. ie no stupid daily standup and scrum master, just a merge meeting between a branch/ main master and people working on a feature branch or soemthing like that. That way you can define best practises but actually tie them down to something tangible without needing endless books on project management buzzwords.
