GitHub Community
Question on how I should handle releases #31899
Answered
by
radar-blip
DylanDevelops
asked this question in
Other Feature Feedback, Questions, & Ideas
-
|
So I am a game developer and for the first time ever I'm using GitHub to backup my files for making my games. I had a question. When I release a build I release it. After that, I make lots of changes and when I feel like it is ready for a new release I release a new build. I was wondering what the best way of handling this type of thing on GitHub might be. Should I create a new branch that I create all those new changes on and then when I am ready, I push everything from that branch to main? Is that how people handle releases with software and games? I'm kind of new to this so I wanted to hear what you guys had to say. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Answered by
radar-blip
Sep 4, 2022
Replies: 1 comment 2 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sounds to me like you're on the right track, create a branch for testing purposes, and when everything is to your liking, merge it into the main branch. Then of course, create a new release.
Here is a quick read about branches.