UE5 with Github as a Source Control

Hello, i have a question regarding Unreal Engine 5. Creating in github a workflow code that uses the UE5 engine to test the .cpp & .h files is there a possible way to combine ue5 with github source control because i’ve been searching around a long time for answers and didn’t find a way to execute what i needed

Basically what i want is to be able in github to check for the same errors or warnings in .cpp and .h files as the we can see in the visual studio code with ue5 checking for syntax and so on.

Best regards :slight_smile:

Here’s a tutorial:

1 Like

The Issue is not the publishing to Github but having the workflow up and running to check when pulling or pushing from Github to check syntax as the UE5 does with VS Code, but thank you for trying

I’m not quite sure what you mean. Could you please clarify your objective? And please form your sentences more carefully, by abiding by grammatical rules and taking readability into account so that we can understand you better.

Now, if you mean you want to be able to detect syntax errors on Git, I don’t think there’s an intended way of achieving that. I don’t see how that could be useful anyway. Though I found this: The Universe of Disco : Automatically checking for syntax errors with Git's pre-commit hook

Maybe this can help :blush:

What i meant is imagine i’m working on a Project right. Let’s say i finished the code and i want to commit to Github to a sub branch not the main branch i want to have a workflow in place so that when i commit changes to github the workflow will be fired up and do the initialization of the repo, build the project and check/compile the project to make sure it is working correctly no errors and warnings appearing and then create an artifact so that i’m able to use it for the releases.

You can try checking out the article I provided in my previous post but it’s not gonna be sufficient for what you have in mind. You’d need to do figure out some stuff yourself. But in my opinion, it will be an unnecessary effort. Why would you need Git to tell you if there’re errors in your source code anyway? You can learn that beforehand on VS. You can test your project before pushing your commit, and errors will be outputted in the log if there are any. There can also be errors like dividing by zero mistakes that can’t be detected on compilation. Plus, no errors doesn’t mean everything’s gonna be working to your expectations! So we can’t talk about an automation process here.

I hope I was able to clear up some of your confusion :innocent:

Thank you for your input. It is my first time building a big project after making so many little projects that i wanted to clarify to get the best idea/approach.

Would you recommend then using Github without Workflows since it’s difficult to find a answer around it, knowing that the testing could be done in the editor in vs code itself.

Sorry for wasting your time, just trying to make sure that i start correctly you know

What about creating releases i wouldn’t need to create a workflow for it if i remember correctly i don’t need a workflow for it right?

No problem :blush:

You see, Git is a version control system. You don’t compile your code or check for errors there. It’s purpose is to store the previous versions of your project, so if something unexpected happens, you can have a chance of reverting to an older version.

There’s something important to note here though. Just a version control is not enough to be safe. I recommend having backup(s) of your project that is / are not connected to any version controls. You can store them in your local machine, a remote machine, or another drive. The reason for this is because sometimes corruption issues cannot be resolved by reverting to an older version, and sometimes it might even not be possible to revert! So take your precautions to make sure that your progress doesn’t get lost.

As for your question, the thing you mentioned can actually be useful even in solo projects. However, it’s not necessary. Especially in your case, where you’re not comfortable with the interface yet, I’d recommend just pushing your commits on a single branch. So don’t get in that stuff. Just push your commits on milestones, also copy your project while you’re doing that, and you should be good! :innocent:

Yes, already have the local backup in place thank you so much for your help.
Have a great rest of your day.
:slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.