How to Release Code With Github

u r so good in explaining the stuff. Bravo!

Thank you! Great video

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

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?

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.

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)?

thanks bro

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

Thank you so much! 🙂

Excelent tutorial. Thank you so much

How to release code with github - Click on "create release" link... Welcome!

Great explanation! Thanks.

Nice video.

Good Explanation!

Thanks a lot.

Thank you very much

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

wonderful explanation straight to action

Thanks. Clear cut explanation.

Thanks for this great video tutorial!

Wow !! you were so clear in explanation.

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

Only Apple products... of course..

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.

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

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?

nice explanation, thank you

Great video, thanks

awesome!!! Thanks a lot.

Great explanation, Sir. Thanks.

When ever I deploy i need the version to change and that version number to be reflected in my web app service. I use ci/cd pipeline azure devops, i take my repos from github. I want you to help me how to do reflect the version number in azure webapp.

Useful content & good content 10/10

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.

This is the best explanation.

Learned a lot in 7 minutes, thanks!

Well explained, Very helpfull, thanks

such a great video thanks

👍

How do i install the metamask 9.8.4?

Very helpful, thank you!

Thank you

Perfect. Thank you

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