Removed the checklist item for ensuring CI is passing. We don't really have CI as of yet and it's confusing to list that requirement. If we do add CI, we'll make it required instead of adding it to the template checklist.
Adds clarification around our expectations for contributions and
how contributions will be handled when they don't meet our requirements.
Updates template to lean into our contribution guidelines.
Cleans up duplicate wording around our contribution guidelines.
ConTeXt generates .tua and .tuc files (utility cache) during each run. These files store document metadata between compilations and are not part of the source, so they should be ignored.
As of Godot 4.2 the editor has a Windows-specific workaround for loading extension libraries.
Before the extension library is loaded the Godot editor creates a temp copy of the extension library `.dll` file with a `~` prefix (e.g. `example.dll` => `~example.dll`).
When the extension library is unloaded the Godot editor deletes the temp copy.
These copied `~*.dll` files are temporary and should be ignored.
References:
Godot 4.2 changelog
https://godotengine.org/article/godot-4-2-arrives-in-style/#gdextension
Godot PR #80188 GDExtension: Copy DLL to a temp file before opening
https://github.com/godotengine/godot/pull/80188
oh-my-opencode excludes the sisyphus working directory in their own repo, so it seems to be best practice. Also, the directory captures agent/runtime state, so it should not be shared.
Updated the days before closing stale PRs from 180 to 365. Due to internal priorities we need to allow more time for PR reviews.
Based on my reading, we need to increase `days-before-close` to ensure that any PR marked with the `stale` label currently benefits from the extension.
Once we are caught up on the backlog, we can revisit this setting.
Cribbed directly from the Element Flatpak's .gitignore file at
https://github.com/flathub/im.riot.Riot/blob/master/.gitignore, simply
because Element is a pretty popular application.
Note in particular that this covers all directories that will be
created by the Flatpak tutorial's suggested `flatpak-builder` command:
https://docs.flatpak.org/en/latest/first-build.html#build-and-install
`repo` is the OSTree repository that the built Flatpak will be
"published" to for testing, `.flatpak-builder` is an internal build
directory, and `builddir` is another, user-specified build directory.
Daniel Johnson