Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Luau.gitignore #4597

Merged
merged 2 commits into from
Mar 12, 2025
Merged

Create Luau.gitignore #4597

merged 2 commits into from
Mar 12, 2025

Conversation

m4fh
Copy link
Contributor

@m4fh m4fh commented Mar 4, 2025

As far as I can tell, there is no official documentation outlining which files should be ignored when using the Luau language. However, there are a few files that can be generated by Luau (or by perfgraph, a recommended tool included in the language repository), namely coverage.out, profile.out, profile.svg, and trace.json—the latter specifically requiring the compiler to be built with LUAU_ENABLE_TIME_TRACE enabled. All of these files have been included in this PR.

Luau is also commonly used alongside a tool called Rojo and an LSP like JohnnyMorganz's luau-lsp. Developers generally choose to ignore files like *.rbxlx.lock, *.rbxl.lock, and sourcemap.json. But I think this would require a separate PR (perhaps a Rojo.gitignore?).

I’m not affiliated with the Luau project, but I believe this .gitignore file could be quite helpful to others, just as it has been to me.

@wirecat
Copy link
Collaborator

wirecat commented Mar 7, 2025

@m4fh Good instincts. We would prefer a seperate template for Rojo.

@m4fh m4fh requested a review from wirecat March 7, 2025 20:36
@wirecat
Copy link
Collaborator

wirecat commented Mar 12, 2025

@m4fh Thank you for the contributions! Looks good. :)

@wirecat wirecat merged commit 5b0261b into github:main Mar 12, 2025
@m4fh m4fh deleted the luau branch March 12, 2025 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants