How to Release Code With Github

[@KahanDataSolutions]

Want to build a reliable, modern data architecture without the mess? Here’s a free checklist to help you → bit.ly/kds-checklist

[@strangescott90]

Pretty much a straight forward video information, not so many people know how to create these kind of good videos explaining stuff

[@KahanDataSolutions]

I appreciate that! Thanks for watching.

[@roshanadhikari5326]

Great content! Short, simple and to the point. Thanks so so much for this.

[@KahanDataSolutions]

You're very welcome!

[@notme222]

I appreciate your clear style of explanation. :) What I'd like to do is have github handle the pushing of published updates to the production server. I think I get the gist that I could create an action to sync the git via sftp automatically after a publish. But frequently I also need to make a database change simultaneously, and making that happen automatically might just be more trouble than it's worth.

[@KahanDataSolutions]

Thanks for the kind words! One thing that you may want to look into for those database changes is Infrastructure as Code (IaC), in particular a tool like Terraform. With that kind of tool, you can automate some of your DB changes and include it in the Github Actions as well. It will take some time to get that part written up and a bit of a learning curve, but will could be super helpful in your case in the long run.

[@notme222]

@@KahanDataSolutions Good to know, thank you very much!

[@mazharkhan5462]

u r so good in explaining the stuff. Bravo!

[@masoodhussain453]

Clear Explanation, Appreciated !

[@FugalBaboon]

Learned a lot in 7 minutes, thanks!

[@KahanDataSolutions]

Glad to hear it! Thanks for watching

[@nicky_rads]

nicely done, found this video very helpful preparing for a release.

[@coderluffy6387]

This is the best explanation.

[@KahanDataSolutions]

Thanks!

[@kaelandchatman4780]

That was really helpful. Thank you!

[@salmansayyad4522]

Thanks for this wonderful content

[@ScrolltheNature]

Wow !! you were so clear in explanation.

[@KahanDataSolutions]

Thanks!

[@sevdalink6676]

Great video. What about including all the commits in the release details? Will that be included automatically or do we have to write it by hand (every commit or branch and what changes it brings)?

[@jysngify]

wonderful explanation straight to action

[@KahanDataSolutions]

Thanks!

[@supersakib62]

Thanks. Clear cut explanation.

[@KahanDataSolutions]

Glad it was helpful!

[@Hackenbaker]

Great explanation, Sir. Thanks.

[@KahanDataSolutions]

You're welcome, thanks for watching!

[@donniedorko3336]

Perfect. Thank you

[@KahanDataSolutions]

You're welcome!

[@alpachino468]

I've never started a release directly on GitHub before, I usually use Gitflow to create a new release, but I'm trying to change my workflow to phase out Gitflow. My question is: If I have a VERSION file within my repo, at what stage do I update this to reflect the new version number? Do I update it within my 'develop' branch, and then create a pull-request - or would I edit it directly within my main/master branch after I create a release directly on Github?

[@mr_phamtastic]

Thanks for this great video tutorial!

[@KahanDataSolutions]

You're very welcome!

[@benrogers5736]

Great explanation! Thanks.

[@KahanDataSolutions]

Glad it was helpful!

[@juanayabaca9529]

Excelent tutorial. Thank you so much

[@KahanDataSolutions]

Glad it was helpful!

[@cs-gl2dm]

HI, I searched many places to find the automation script documentation for release. I couldn't find. Can you please share that?

[@elvistejeda8661]

Very helpful, thank you!

[@KahanDataSolutions]

You're welcome!

[@kunjeshramani649]

Good Explanation!

[@KahanDataSolutions]

Glad it was helpful!

[@johnywhy4679]

4:56 Why don't you click "Publish your first package"?

[@surjithctly]

Imagine we released a software with version v1.0.0. Now we are working on our next major version v2.0.0 by commiting all new changes in the "main" branch. Now one of our user discovered a bug in v1.0.0 and we have to release a bug fix with v1.0.1, but we already had commits for v2, so we can't use "main" for the patch release. So how do we manage this situation? what's the best way to manage tags/release in this case?

[@RabindraNathMurmuready2upload]

you can rewrite history use `git rebase -i head~3` to rearrange commits cherry pick the bug fix patch and commit

[@surjithctly]

@@RabindraNathMurmuready2upload Is this how popular repos are managed? coz they are having multiple releases and maintainers. git rebase make sense for them?

[@Jose_T131]

Useful content & good content 10/10

[@KahanDataSolutions]

Much appreciated!

[@chconnect]

Well explained, Very helpfull, thanks

[@KahanDataSolutions]

Glad it was helpful, thanks for watching

[@markokraljevic1590]

nice explanation, thank you

[@KahanDataSolutions]

Thanks for watching

[@ErickJeronimo]

Great video, thanks

[@KahanDataSolutions]

Thanks for watching!

[@hritikkumar2554]

Thank you very much❤

[@MikhailRumyantsev-r1n]

Thank you so much! 🙂

[@AlphaSierra380]

Nice video.

[@KahanDataSolutions]

Thanks!

[@kareenmarie8586]

such a great video thanks

[@KahanDataSolutions]

Glad it was helpful, thanks for watching

[@adelhaiba]

Thank you very much

[@KahanDataSolutions]

No problem, thanks for watching

[@Saranwity]

awesome!!! Thanks a lot.

[@KahanDataSolutions]

You're welcome!

[@DeepAmbientDrone]

Is there a way to set permissions or visibility for assets? For instance, I want only to publish/release installation files and not the code of my software. Edit: I would like to add that I am using automatic releasing in vscode. The source code (zip) file seems to be automatically created by github in the assets based on the code in the main repository and cannot be removed from the assets. A possible solution for my problem would be to use 2 different repositories in github. One repository contains the code and is private and the public repository is where the releases are published. It is a bit messy if you then have an empty source code file in the assets, but at least the code is not published this way. I have not yet found another solution.

[@khumozin]

Thank you

[@KahanDataSolutions]

You're welcome

[@maharun]

Thanks a lot.

[@srini580]

thanks!

[@ПетрМельник-к4х]

how do i add a new release? I can only edit the old one.

[@KoreanLabx]

I disagree with compatibility stuff when major changes. Most of libraries are compatible even though they increase major number. If it's not compatible, then the users will no longer use that library.

[@noahthegreat190]

thanks bro

[@ruixue6955]

4:42 demo

[@frroossst4267]

👍

[@ralkey]

i dont have access to releases on my own repo as in it doesnt exist what do i do now?

[@KahanDataSolutions]

Perhaps you have limited permissions. Are you the owner of the repository?

[@ralkey]

@@KahanDataSolutions yes it is my repository

[@maghiiTM]

@@ralkey I had the same problem. I figured I was not logged in, can you check if you had logged in to your account?

[@ralkey]

@@maghiiTM ah no i figured it out. One of my chrome extensions removed the releases tab. So i deleted that extension

[@diderror]

- 4.37 минуте беларуска вова, падабайка за гэта!

[@LarsRyeJeppesen]

Only Apple products... of course..

[@MrZackmedia]

watching this videos as a BE dev, what a waste of my time. uselessness waste of my time

[@NursultanBegaliev]

Thank you! Great video