How do GitHub Actions work in a Godot repository and how are Godot releases created?

Hello. I’m trying to understand how GitHub Actions works in a Godot repository. When all Jobs are completed, the following Artifacts appear as a result as in the screenshot.

  1. Please tell me which of these builds later become Godot 4 releases? Or are releases created in some other way, not using GitHub Actions? Then how are releases created?

  2. Why, for example, does Windows have “windows-editor” and “windows-template”, and Linux has “linux-editor-mono”, “linux-template-minimal” and “linux-template-mono”? Why doesn’t Linux have a version without mono?


  1. Release builds are compiled separately on a dedicated server and not via GitHub actions. Their compilation is triggered manually by the production team.
  2. The versions, that are build, are manually selected. They are chosen in a way to maximize the amount of different tool-chains tested, given the limited available resources. One additional place to look for answers is the commit history of the file, responsible for Linux GitHub Actions: History for .github/workflows/linux_builds.yml - godotengine/godot · GitHub
2 Likes

Hello, thank you very much for your answer!

Please tell me, do you think there is somewhere I can get more detailed information about this dedicated server you are talking about? For example, I’m interested in what operating system is there or are there containers with different operating systems? What software is used? Apparently SCons is used as it is written in the documentation, but perhaps something else is used.

If you or anyone has more details, I would appreciate any details :slightly_smiling_face:

this links maybe helpfull

2 Likes

Thank you very much!