How to Release Code With Github

  Рет қаралды 99,027

Kahan Data Solutions

Kahan Data Solutions

Күн бұрын

Пікірлер: 80
@KahanDataSolutions
@KahanDataSolutions 3 жыл бұрын
Looking for help with your team's data strategy? → www.kahandatasolutions.com Looking to improve your data engineering skillset?→ bit.ly/more-kds
@strangescott90
@strangescott90 2 жыл бұрын
Pretty much a straight forward video information, not so many people know how to create these kind of good videos explaining stuff
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
I appreciate that! Thanks for watching.
@roshanadhikari5326
@roshanadhikari5326 2 жыл бұрын
Great content! Short, simple and to the point. Thanks so so much for this.
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
You're very welcome!
@notme222
@notme222 2 жыл бұрын
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
@KahanDataSolutions 2 жыл бұрын
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
@notme222 2 жыл бұрын
@@KahanDataSolutions Good to know, thank you very much!
@mazharkhan5462
@mazharkhan5462 Жыл бұрын
u r so good in explaining the stuff. Bravo!
@FugalBaboon
@FugalBaboon 2 жыл бұрын
Learned a lot in 7 minutes, thanks!
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Glad to hear it! Thanks for watching
@sevdalink6676
@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)?
@kaelandchatman4780
@kaelandchatman4780 Ай бұрын
That was really helpful. Thank you!
@johnywhy4679
@johnywhy4679 2 жыл бұрын
4:56 Why don't you click "Publish your first package"?
@salmansayyad4522
@salmansayyad4522 2 ай бұрын
Thanks for this wonderful content
@nicky_rads
@nicky_rads Жыл бұрын
nicely done, found this video very helpful preparing for a release.
@coderluffy6387
@coderluffy6387 2 жыл бұрын
This is the best explanation.
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Thanks!
@donniedorko3336
@donniedorko3336 3 жыл бұрын
Perfect. Thank you
@KahanDataSolutions
@KahanDataSolutions 3 жыл бұрын
You're welcome!
@alpachino468
@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?
@ScrolltheNature
@ScrolltheNature 2 жыл бұрын
Wow !! you were so clear in explanation.
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Thanks!
@supersakib62
@supersakib62 2 жыл бұрын
Thanks. Clear cut explanation.
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Glad it was helpful!
@jysngify
@jysngify 2 жыл бұрын
wonderful explanation straight to action
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Thanks!
@kunjeshramani649
@kunjeshramani649 2 жыл бұрын
Good Explanation!
@KahanDataSolutions
@KahanDataSolutions Жыл бұрын
Glad it was helpful!
@elvistejeda8661
@elvistejeda8661 2 жыл бұрын
Very helpful, thank you!
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
You're welcome!
@Hackenbaker
@Hackenbaker 2 жыл бұрын
Great explanation, Sir. Thanks.
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
You're welcome, thanks for watching!
@benrogers5736
@benrogers5736 Жыл бұрын
Great explanation! Thanks.
@KahanDataSolutions
@KahanDataSolutions Жыл бұрын
Glad it was helpful!
@mr_phamtastic
@mr_phamtastic 2 жыл бұрын
Thanks for this great video tutorial!
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
You're very welcome!
@juanayabaca9529
@juanayabaca9529 Жыл бұрын
Excelent tutorial. Thank you so much
@KahanDataSolutions
@KahanDataSolutions Жыл бұрын
Glad it was helpful!
@ПетрМельник-к4х
@ПетрМельник-к4х 2 жыл бұрын
how do i add a new release? I can only edit the old one.
@DeepAmbientDrone
@DeepAmbientDrone 2 жыл бұрын
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.
@Jose_T131
@Jose_T131 2 жыл бұрын
Useful content & good content 10/10
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Much appreciated!
@MikhailRumyantsev-r1n
@MikhailRumyantsev-r1n Жыл бұрын
Thank you so much! 🙂
@hritikkumar2554
@hritikkumar2554 9 ай бұрын
Thank you very much❤
@chconnect
@chconnect 2 жыл бұрын
Well explained, Very helpfull, thanks
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Glad it was helpful, thanks for watching
@ErickJeronimo
@ErickJeronimo 2 жыл бұрын
Great video, thanks
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Thanks for watching!
@markokraljevic1590
@markokraljevic1590 2 жыл бұрын
nice explanation, thank you
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Thanks for watching
@AlphaSierra380
@AlphaSierra380 Жыл бұрын
Nice video.
@KahanDataSolutions
@KahanDataSolutions Жыл бұрын
Thanks!
@surjithctly
@surjithctly 2 жыл бұрын
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
@RabindraNathMurmuready2upload 2 жыл бұрын
you can rewrite history use `git rebase -i head~3` to rearrange commits cherry pick the bug fix patch and commit
@surjithctly
@surjithctly 2 жыл бұрын
@@RabindraNathMurmuready2upload Is this how popular repos are managed? coz they are having multiple releases and maintainers. git rebase make sense for them?
@kareenmarie8586
@kareenmarie8586 2 жыл бұрын
such a great video thanks
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
Glad it was helpful, thanks for watching
@Saranwity
@Saranwity 2 жыл бұрын
awesome!!! Thanks a lot.
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
You're welcome!
@adelhaiba
@adelhaiba 2 жыл бұрын
Thank you very much
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
No problem, thanks for watching
@maharun
@maharun 2 жыл бұрын
Thanks a lot.
@khumozin
@khumozin 2 жыл бұрын
Thank you
@KahanDataSolutions
@KahanDataSolutions 2 жыл бұрын
You're welcome
@ruixue6955
@ruixue6955 Жыл бұрын
4:42 demo
@srini580
@srini580 5 ай бұрын
thanks!
@KoreanLabx
@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.
@ralkey
@ralkey 3 жыл бұрын
i dont have access to releases on my own repo as in it doesnt exist what do i do now?
@KahanDataSolutions
@KahanDataSolutions 3 жыл бұрын
Perhaps you have limited permissions. Are you the owner of the repository?
@ralkey
@ralkey 3 жыл бұрын
@@KahanDataSolutions yes it is my repository
@maghiiTM
@maghiiTM 2 жыл бұрын
@@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
@ralkey 2 жыл бұрын
@@maghiiTM ah no i figured it out. One of my chrome extensions removed the releases tab. So i deleted that extension
@frroossst4267
@frroossst4267 2 жыл бұрын
👍
@diderror
@diderror Жыл бұрын
- 4.37 минуте беларуска вова, падабайка за гэта!
@LarsRyeJeppesen
@LarsRyeJeppesen 2 жыл бұрын
Only Apple products... of course..
@MrZackmedia
@MrZackmedia 5 ай бұрын
watching this videos as a BE dev, what a waste of my time. uselessness waste of my time
@NursultanBegaliev
@NursultanBegaliev Жыл бұрын
Thank you! Great video
Branching Strategies Explained
18:19
DevOps Toolkit
Рет қаралды 144 М.
“Don’t stop the chances.”
00:44
ISSEI / いっせい
Рет қаралды 61 МЛН
REAL or FAKE? #beatbox #tiktok
01:03
BeatboxJCOP
Рет қаралды 17 МЛН
A typical GitHub workflow // what to expect
10:00
Kahan Data Solutions
Рет қаралды 23 М.
How to Manage Releases with Semantic Versioning and Git Tags
43:14
Use Outputs to Share Data Between Jobs // GitHub Actions
14:37
Kahan Data Solutions
Рет қаралды 9 М.
Fully Automated npm publish using GitHub Actions and Semantic Release
26:24
GitHub Basics Made Easy: A Fast Beginner's Tutorial!
23:30
Skill Foundry
Рет қаралды 209 М.
Strategies for Github Tagging and Release Management
21:01
Wazoo Web Bytes
Рет қаралды 2,8 М.
Automate your GitHub Actions Releases (with Semantic Release)!
23:39
Dave's Dev Channel
Рет қаралды 36 М.
Git and GitHub for Beginners - Crash Course
1:08:30
freeCodeCamp.org
Рет қаралды 4,3 МЛН
So You Think You Know Git - FOSDEM 2024
47:00
GitButler
Рет қаралды 1,3 МЛН
“Don’t stop the chances.”
00:44
ISSEI / いっせい
Рет қаралды 61 МЛН