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.
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.
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)?
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?
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.
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 Is this how popular repos are managed? coz they are having multiple releases and maintainers. git rebase make sense for them?
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.
Deliver more impact w/ modern data tools, without getting overwhelmed
See how in The Starter Guide for Modern Data → www.kahandatasolutions.com/guide
Pretty much a straight forward video information, not so many people know how to create these kind of good videos explaining stuff
I appreciate that! Thanks for watching.
Great content! Short, simple and to the point. Thanks so so much for this.
You're very welcome!
u r so good in explaining the stuff. Bravo!
That was really helpful. Thank you!
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.
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.
@@KahanDataSolutions Good to know, thank you very much!
Thanks for this wonderful content
This is the best explanation.
Thanks!
Learned a lot in 7 minutes, thanks!
Glad to hear it! Thanks for watching
nicely done, found this video very helpful preparing for a release.
Thanks. Clear cut explanation.
Glad it was helpful!
Wow !! you were so clear in explanation.
Thanks!
wonderful explanation straight to action
Thanks!
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)?
Great explanation, Sir. Thanks.
You're welcome, thanks for watching!
Perfect. Thank you
You're welcome!
Good Explanation!
Glad it was helpful!
Thanks for this great video tutorial!
You're very welcome!
Great explanation! Thanks.
Glad it was helpful!
Excelent tutorial. Thank you so much
Glad it was helpful!
Very helpful, thank you!
You're welcome!
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?
4:56 Why don't you click "Publish your first package"?
Useful content & good content 10/10
Much appreciated!
Well explained, Very helpfull, thanks
Glad it was helpful, thanks for watching
Thank you very much❤
Thank you so much! 🙂
Great video, thanks
Thanks for watching!
nice explanation, thank you
Thanks for watching
Nice video.
Thanks!
Thank you very much
No problem, thanks for watching
Thanks a lot.
such a great video thanks
Glad it was helpful, thanks for watching
awesome!!! Thanks a lot.
You're welcome!
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.
thanks!
4:42 demo
how do i add a new release? I can only edit the old one.
Thank you
You're welcome
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?
you can rewrite history
use `git rebase -i head~3` to rearrange commits
cherry pick the bug fix patch and commit
@@RabindraNathMurmuready2upload Is this how popular repos are managed? coz they are having multiple releases and maintainers. git rebase make sense for them?
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.
👍
i dont have access to releases on my own repo
as in it doesnt exist
what do i do now?
Perhaps you have limited permissions. Are you the owner of the repository?
@@KahanDataSolutions yes it is my repository
@@ralkey I had the same problem. I figured I was not logged in, can you check if you had logged in to your account?
@@maghiiTM ah no i figured it out. One of my chrome extensions removed the releases tab. So i deleted that extension
- 4.37 минуте беларуска вова, падабайка за гэта!
Only Apple products... of course..
watching this videos as a BE dev, what a waste of my time. uselessness waste of my time
Thank you! Great video