| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Also includes #71080.
Co-authored-by: Psychpsyo <60073468+Psychpsyo@users.noreply.github.com>
|
|
The field is now required, but "N/A" can be manually entered if
the reproduction steps are trivial and don't require any project
files to be followed.
|
|
Fully removes the `bits` option and adapts the code that relied on it.
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
|
|
As announced in https://godotengine.org/article/godot-4-will-discontinue-visual-scripting,
Godot maintainers have agreed to discontinue the current implementation of
our VisualScript language.
The way it had been designed was not user-friendly enough and we did not
succeed in improving its usability to actually make it a good low-code
solution for users who need one.
So we prefer to remove it for Godot 4.0 and leave the door open for new,
innovative ideas around visual scripting, to be developed as plugins or
extensions now that Godot provides sufficient functionality for this
(notably via GDExtension and the godot-cpp C++ bindings).
The current module has been moved to a dedicated repository (with full Git
history extracted with `git filter-branch`):
https://github.com/godotengine/godot-visual-script
It can still be compiled as a C++ module (for now, but will likely require
work to be kept in sync with the engine repository), but our hope is that
contributors will port it to GDExtension (which is quite compatibile with
the existing C++ module code when using the godot-cpp C++ bindings).
|
|
Third-party file hosts can have their files expire or be removed
by the owner. In comparison, GitHub attachments are more resilient.
This also fixes the link to create a bug report.
|
|
|
|
Many contributors don't have a Mono setup available, especially if
compiling from source is required.
Minimal reproduction projects in GDScript are also better at isolating
the actual bug, since it automatically rules out any possible C#
integration issues.
|
|
This partially addresses
https://github.com/godotengine/godot-proposals/issues/1586.
|
|
Documenting new additions has been an informal requirement for
a few months now. This makes it official.
|
|
- Improve the bug reporting guidelines for readability.
- Make some guidelines more strictly applied in the interest of
bug report quality.
- Mention that feature proposals should now be opened on the
Godot Proposals repository.
- Update the Git commit message guide to be easier to follow.
- Fix warnings reported by markdownlint.
|
|
|
|
|
|
CONTRIBUTING.md would use the phrase "those guidelines" to introduce a
list. In general, the word "these" is used to refer to something that is
being introduced or has recently been introduced, and "those" is used to
refer to something that had been previously introduced.
This change also makes CONTRIBUTING.md consistent with the
documentation. The documentation guidelines at
https://docs.godotengine.org/en/latest/community/contributing/documentation_guidelines.html
use "these" to introduce a list and its singular form, "this", to
introduce items.
|
|
|
|
Fixes #23509.
|
|
|
|
|
|
|
|
Added a little paragraph about how to contribute to Godot's translations
|
|
This is a really minor change. I just changed the link to the IRC channel login from http to https.
Thank you! ^ _ ^
|
|
From https://github.com/lucasdemarchi/codespell
|
|
|
|
|
|
|
|
|
|
|
|
|