Rebrand Godot to Redot

.git-blame-ignore-revs

@@ -57,3 +57,6 @@ df61dc4b2bd54a5a40c515493c76f5a458e5b541
 
 # Style: Apply new `clang-format` fixes
 b37fc1014abf7adda70dc30b0822d775b3a4433f
+
+# Rebrand preambles to Redot
+e8542b06acca3c1bdeee4b528411771f0819f084

.github/workflows/linux_builds.yml

@@ -23,11 +23,22 @@ jobs:
  fail-fast: false
  matrix:
  include:
+ - name: Editor (target=editor tests=yes)
+ cache-name: linux-editor
+ target: editor
+ bin: ./bin/redot.linuxbsd.editor.x86_64
+ build-mono: false
+ tests: true
+ doc-test: true
+ proj-conv: true
+ api-compat: true
+ artifact: true
+
  - name: Editor w/ Mono (target=editor)
  cache-name: linux-editor-mono
  target: editor
  sconsflags: module_mono_enabled=yes
- bin: ./bin/godot.linuxbsd.editor.x86_64.mono
+ bin: ./bin/redot.linuxbsd.editor.x86_64.mono
  build-mono: true
  tests: false # Disabled due freeze caused by mix Mono build and CI
  doc-test: true
@@ -40,7 +51,7 @@ jobs:
  target: editor
  # Debug symbols disabled as they're huge on this build and we hit the 14 GB limit for runners.
  sconsflags: dev_build=yes scu_build=yes debug_symbols=no precision=double use_asan=yes use_ubsan=yes linker=gold
- bin: ./bin/godot.linuxbsd.editor.dev.double.x86_64.san
+ bin: ./bin/redot.linuxbsd.editor.dev.double.x86_64.san
  build-mono: false
  tests: true
  proj-test: true
@@ -53,7 +64,7 @@ jobs:
  cache-name: linux-editor-llvm-sanitizers
  target: editor
  sconsflags: dev_build=yes use_asan=yes use_ubsan=yes use_llvm=yes linker=lld
- bin: ./bin/godot.linuxbsd.editor.dev.x86_64.llvm.san
+ bin: ./bin/redot.linuxbsd.editor.dev.x86_64.llvm.san
  build-mono: false
  tests: true
  # Skip 2GiB artifact speeding up action.
@@ -66,7 +77,7 @@ jobs:
  target: editor
  tests: true
  sconsflags: dev_build=yes use_tsan=yes use_llvm=yes linker=lld
- bin: ./bin/godot.linuxbsd.editor.dev.x86_64.llvm.san
+ bin: ./bin/redot.linuxbsd.editor.dev.x86_64.llvm.san
  build-mono: false
  # Skip 2GiB artifact speeding up action.
  artifact: false
@@ -75,7 +86,7 @@ jobs:
  cache-name: linux-template-mono
  target: template_release
  sconsflags: module_mono_enabled=yes
- bin: ./bin/godot.linuxbsd.template_release.x86_64.mono
+ bin: ./bin/redot.linuxbsd.template_release.x86_64.mono
  build-mono: false
  tests: true
  artifact: true
@@ -84,7 +95,7 @@ jobs:
  cache-name: linux-template-minimal
  target: template_release
  sconsflags: modules_enabled_by_default=no disable_3d=yes disable_advanced_gui=yes deprecated=no minizip=no
- bin: ./bin/godot.linuxbsd.template_release.x86_64
+ bin: ./bin/redot.linuxbsd.template_release.x86_64
  tests: true
  artifact: true
 
@@ -162,8 +173,8 @@ jobs:
  - name: Prepare artifact
  if: matrix.artifact
  run: |
- strip bin/godot.*
- chmod +x bin/godot.*
+ strip bin/redot.*
+ chmod +x bin/redot.*
 
  - name: Upload artifact
  uses: ./.github/actions/upload-artifact

.github/workflows/macos_builds.yml

@@ -24,14 +24,14 @@ jobs:
  cache-name: macos-editor
  target: editor
  tests: true
- bin: ./bin/godot.macos.editor.universal
+ bin: ./bin/redot.macos.editor.universal
 
  - name: Template (target=template_release, tests=yes)
  cache-name: macos-template
  target: template_release
  tests: true
  sconsflags: debug_symbols=no
- bin: ./bin/godot.macos.template_release.universal
+ bin: ./bin/redot.macos.template_release.universal
 
  steps:
  - name: Checkout
@@ -76,10 +76,10 @@ jobs:
 
  - name: Prepare artifact
  run: |
- lipo -create ./bin/godot.macos.${{ matrix.target }}.x86_64 ./bin/godot.macos.${{ matrix.target }}.arm64 -output ./bin/godot.macos.${{ matrix.target }}.universal
- rm ./bin/godot.macos.${{ matrix.target }}.x86_64 ./bin/godot.macos.${{ matrix.target }}.arm64
- strip bin/godot.*
- chmod +x bin/godot.*
+ lipo -create ./bin/redot.macos.${{ matrix.target }}.x86_64 ./bin/redot.macos.${{ matrix.target }}.arm64 -output ./bin/redot.macos.${{ matrix.target }}.universal
+ rm ./bin/redot.macos.${{ matrix.target }}.x86_64 ./bin/redot.macos.${{ matrix.target }}.arm64
+ strip bin/redot.*
+ chmod +x bin/redot.*
 
  - name: Upload artifact
  uses: ./.github/actions/upload-artifact

.github/workflows/static_checks.yml

@@ -26,19 +26,19 @@ jobs:
  pip3 install pytest==7.1.2
  git config diff.wsErrorHighlight all
 
- - name: Get changed files
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- run: |
- if [ "${{ github.event_name }}" == "pull_request" ]; then
- files=$(git diff-tree --no-commit-id --name-only -r HEAD^1..HEAD 2> /dev/null || true)
- elif [ "${{ github.event_name }}" == "push" -a "${{ github.event.forced }}" == "false" -a "${{ github.event.created }}" == "false" ]; then
- files=$(git diff-tree --no-commit-id --name-only -r ${{ github.event.before }}..${{ github.event.after }} 2> /dev/null || true)
- fi
- echo "$files" >> changed.txt
- cat changed.txt
- files=$(echo "$files" | grep -v 'thirdparty' | xargs -I {} sh -c 'echo "\"./{}\""' | tr '\n' ' ')
- echo "CHANGED_FILES=$files" >> $GITHUB_ENV
+ # - name: Get changed files
+ #  env:
+ #  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ #  run: |
+ #  if [ "${{ github.event_name }}" == "pull_request" ]; then
+ #  files=$(git diff-tree --no-commit-id --name-only -r HEAD^1..HEAD 2> /dev/null || true)
+ #  elif [ "${{ github.event_name }}" == "push" -a "${{ github.event.forced }}" == "false" -a "${{ github.event.created }}" == "false" ]; then
+ #  files=$(git diff-tree --no-commit-id --name-only -r ${{ github.event.before }}..${{ github.event.after }} 2> /dev/null || true)
+ #  fi
+ #  echo "$files" >> changed.txt
+ #  cat changed.txt
+ #  files=$(echo "$files" | grep -v 'thirdparty' | xargs -I {} sh -c 'echo "\"./{}\""' | tr '\n' ' ')
+ #  echo "CHANGED_FILES=$files" >> $GITHUB_ENV
 
  # This needs to happen before Python and npm execution; it must happen before any extra files are written.
  - name: .gitignore checks (gitignore_check.sh)

.github/workflows/windows_builds.yml

@@ -29,22 +29,34 @@ jobs:
  tests: true
  # Skip debug symbols, they're way too big with MSVC.
  sconsflags: debug_symbols=no vsproj=yes vsproj_gen_only=no windows_subsystem=console
- bin: ./bin/godot.windows.editor.x86_64.exe
+ bin: ./bin/redot.windows.editor.x86_64.exe
+ artifact: true
+
+ - name: Editor w/ Mono (target=editor)
+ cache-name: windows-editor-mono
+ target: editor
+ sconsflags: module_mono_enabled=yes
+ bin: ./bin/redot.windows.editor.x86_64.mono.exe
+ build-mono: true
+ tests: false # Disabled due freeze caused by mix Mono build and CI
+ doc-test: true
+ proj-conv: true
+ api-compat: true
  artifact: true
 
  - name: Editor w/ clang-cl (target=editor, tests=yes, use_llvm=yes)
  cache-name: windows-editor-clang
  target: editor
  tests: true
  sconsflags: debug_symbols=no windows_subsystem=console use_llvm=yes
- bin: ./bin/godot.windows.editor.x86_64.llvm.exe
+ bin: ./bin/redot.windows.editor.x86_64.llvm.exe
 
  - name: Template (target=template_release, tests=yes)
  cache-name: windows-template
  target: template_release
  tests: true
  sconsflags: debug_symbols=no
- bin: ./bin/godot.windows.template_release.x86_64.console.exe
+ bin: ./bin/redot.windows.template_release.x86_64.console.exe
  artifact: true
 
  steps:
@@ -87,6 +99,14 @@ jobs:
  target: ${{ matrix.target }}
  tests: ${{ matrix.tests }}
 
+ - name: Generate Glue Code
+ if: ${{ matrix.cache-name == 'windows-editor-mono' }}
+ run: ./bin/redot.windows.editor.x86_64.mono.exe --headless --generate-mono-glue modules/mono/glue
+
+ - name: Build GodotSharp
+ if: ${{ matrix.cache-name == 'windows-editor-mono' }}
+ run: python modules/mono/build_scripts/build_assemblies.py --godot-output-dir=./bin
+
  - name: Save Godot build cache
  uses: ./.github/actions/godot-cache-save
  with:

CONTRIBUTING.md

@@ -1,9 +1,9 @@
 # Contributors guidelines
 
 This document summarizes the most important points for people interested in
-contributing to Godot, especially via bug reports or pull requests.
+contributing to Redot, especially via bug reports or pull requests.
 
-The Godot documentation has a dedicated [Contributing section](https://docs.godotengine.org/en/latest/contributing/how_to_contribute.html)
+The [Redot Discord](https://discord.gg/redot) documentation has a dedicated Contributing section
 which details these points and more, and is a recommended read.
 
 ## Table of contents
@@ -16,29 +16,26 @@ which details these points and more, and is a recommended read.
 
 ## Reporting bugs
 
-Report bugs [here](https://github.com/godotengine/godot/issues/new?assignees=&labels=&template=bug_report.yml).
+Report bugs [here](https://github.com/Redot-Engine/redot-engine/issues/new?assignees=&labels=&template=bug_report.yml).
 Please follow the instructions in the template when you do.
 
 Notably, please include a Minimal Reproduction Project (MRP), which is a small
-Godot project which reproduces the issue, with no unnecessary files included.
+Redot project which reproduces the issue, with no unnecessary files included.
 Be sure to not include the `.godot` folder in the archive to save space.
 
-Make sure that the bug you are experiencing is reproducible in the latest Godot
-releases. You can find an overview of all Godot releases [on the website](https://godotengine.org/download/archive/)
-to confirm whether your current version is the latest one. It's worth testing
-against both the latest stable release and the latest dev snapshot for the next
-Godot release.
+Make sure that the bug you are experiencing is reproducible in the latest Redot
+releases. It's worth testing against both the latest stable release and the
+latest dev snapshot for the next Redot release.
 
-If you run into a bug which wasn't present in an earlier Godot version (what we
+If you run into a bug which wasn't present in an earlier Redot version (what we
 call a _regression_), please mention it and clarify which versions you tested
 (both the one(s) working and the one(s) exhibiting the bug).
 
 ## Proposing features or improvements
 
 **The main issue tracker is for bug reports and does not accept feature proposals.**
 
-Instead, head to the [Godot Proposals repository](https://github.com/godotengine/godot-proposals)
-and follow the instructions in the README file and issue template.
+Instead, head to the [Redot Discord](https://discord.gg/redot).
 
 ## Contributing pull requests
 
@@ -55,18 +52,7 @@ Similar rules can be applied when contributing bug fixes - it's always best to
 discuss the implementation in the bug report first if you are not 100% about
 what would be the best fix.
 
-You can refer to the [Pull request review process](https://docs.godotengine.org/en/latest/contributing/workflow/pr_review_guidelines.html)
-for insights into the intended lifecycle of pull requests. This should help you
-ensure that your pull request fulfills the requirements.
-
-In addition to the following tips, also take a look at the
-[Engine development guide](https://docs.godotengine.org/en/latest/contributing/development/index.html)
-for an introduction to developing on Godot.
-
-The [Contributing docs](https://docs.godotengine.org/en/latest/contributing/how_to_contribute.html)
-also have important information on the [PR workflow](https://docs.godotengine.org/en/latest/contributing/workflow/pr_workflow.html)
-(with a helpful guide for Git usage), and our [Code style guidelines](https://docs.godotengine.org/en/latest/contributing/development/code_style_guidelines.html)
-which all contributions need to follow.
+Visit the [Redot Discord](https://discord.gg/redot) for information and guides related to contribution and pull requests.
 
 ### Be mindful of your commits
 
@@ -84,9 +70,6 @@ stable state, i.e. if your first commit has a bug that you fixed in the second
 commit, try to merge them together before making your pull request. This
 includes fixing build issues or typos, adding documentation, etc.
 
-See our [PR workflow](https://docs.godotengine.org/en/latest/contributing/workflow/pr_workflow.html)
-documentation for tips on using Git, amending commits and rebasing branches.
-
 This [Git style guide](https://github.com/agis-/git-style-guide) also has some
 good practices to have in mind.
 
@@ -125,12 +108,12 @@ description is also manually wrapped at 80 chars for readability):
 ```text
 Prevent French fries carbonization by fixing heat regulation
 
-When using the French fries frying module, Godot would not regulate the heat
+When using the French fries frying module, Redot would not regulate the heat
 and thus bring the oil bath to supercritical liquid conditions, thus causing
 unwanted side effects in the physics engine.
 
 By fixing the regulation system via an added binding to the internal feature,
-this commit now ensures that Godot will not go past the ebullition temperature
+this commit now ensures that Redot will not go past the ebullition temperature
 of cooking oil under normal atmospheric conditions.
 ```
 
@@ -182,32 +165,24 @@ for information on writing tests in Godot's C++ codebase.
 You can contribute to Godot translations on [Hosted Weblate](https://hosted.weblate.org/projects/godot-engine/),
 an open source and web-based translation platform.
 
-Please refer to our [editor and documentation localization guidelines](https://docs.godotengine.org/en/latest/contributing/documentation/editor_and_docs_localization.html)
+Please refer to Godot's [editor and documentation localization guidelines](https://docs.godotengine.org/en/latest/contributing/documentation/editor_and_docs_localization.html)
 for an overview of the translation resources and what they correspond to.
 
 ## Communicating with developers
 
-The Godot Engine community has [many communication
-channels](https://godotengine.org/community), some used more for user-level
-discussions and support, others more for development discussions.
+The Redot Engine community is largely centralized on the [Redot Discord](https://discord.gg/redot) at this time, feel free to drop by!
 
 To communicate with developers (e.g. to discuss a feature you want to implement
 or a bug you want to fix), the following channels can be used:
 
-- [Godot Contributors Chat](https://chat.godotengine.org): You will
- find most core developers there, so it's the go-to platform for direct chat
- about Godot Engine development. Browse the [Directory](https://chat.godotengine.org/directory/channels)
- for an overview of public channels focusing on various engine areas which you
- might be interested in.
-- [Bug tracker](https://github.com/godotengine/godot/issues): If there is an
+- [Redot Discord](https://discord.gg/redot): General community chat and development can all be found here.
+- [Bug tracker](https://github.com/Redot-Engine/redot-engine/issues): If there is an
  existing issue about a topic you want to discuss, you can participate directly.
  If not, you can open a new issue. Please mind the guidelines outlined above
  for bug reporting.
-- [Feature proposals](https://github.com/godotengine/godot-proposals/issues):
- To propose a new feature, we have a dedicated issue tracker for that. Don't
- hesitate to start by talking about your idea on the Godot Contributors Chat
- to make sure that it makes sense in Godot's context.
+- Feature Proposals should be made on the [Redot Discord](https://discord.gg/redot) for now.
+- [Redot](https://x.com/redotengine) on Twitter
 
 Thanks for your interest in contributing!
 
-—The Godot development team
+—Redot Development Community