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

Add static check for overzealous .gitignores and fix an example of such. #78908

Merged
merged 2 commits into from
Aug 29, 2023

Conversation

zorbathut
Copy link
Contributor

This is a followup to #47212.

As part of my project setup, I decompress Godot into its own directory and copy the source across. This is kind of awkward to work with because Godot frequently has parts of its own repository ignored. I've got my scripts hooked up to work around this, but it keeps happening and I really think there should be a static check to solve it.

Enclosed is that static check, along with a fix for the latest example of the problem. If you'd like to see what the error looks like, check out https://github.com/zorbathut/godot/actions/runs/5431343555/jobs/9877648317 which was an intentional failure for testing - note that it also prints the file the ignore comes from. Github lists this process as taking zero seconds; in local testing, it's about 0.04 seconds.

I also tweaked a .gitignore to unignore a directory, though I'm not sure if that was the right solution.

I'm happy to make adjustments!

@akien-mga akien-mga modified the milestones: 4.x, 4.2 Aug 29, 2023
@akien-mga akien-mga added cherrypick:3.x Considered for cherry-picking into a future 3.x release cherrypick:3.5 Considered for cherry-picking into a future 3.5.x release cherrypick:4.0 cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release labels Aug 29, 2023
@akien-mga akien-mga merged commit 5b5471e into godotengine:master Aug 29, 2023
@akien-mga
Copy link
Member

Thanks!

@akien-mga
Copy link
Member

Cherry-picked for 3.6.

@akien-mga akien-mga removed the cherrypick:3.x Considered for cherry-picking into a future 3.x release label Aug 29, 2023
@akien-mga
Copy link
Member

Cherry-picked for 3.5.3. (Only the first commit, not the added CI check as there's still an issue with it #81151.)

@akien-mga akien-mga removed the cherrypick:3.5 Considered for cherry-picking into a future 3.5.x release label Sep 6, 2023
@YuriSizov
Copy link
Contributor

Cherry-picked for 4.1.4. Also just the first commit for the same reason.

@YuriSizov YuriSizov removed the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Jan 23, 2024
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.

3 participants