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

Remove lgtm.yml since LGTM is now replaced by Github Code Scanning #81874

Merged
merged 1 commit into from
Jan 23, 2024

Conversation

mrbbbaixue
Copy link
Contributor

LGTM has been acquired by Github, and all its features is replaced by Github Code Scanning.
So seems .lgtm.yml is no longer used.

Detailed Github announcement here

LGTM has been acquired by Github, and all its features is replaced by Github Code Scanning.
So seems .lgtm.yml is no longer used.
@mrbbbaixue mrbbbaixue requested a review from a team as a code owner September 18, 2023 16:25
@Calinou Calinou added this to the 4.2 milestone Sep 18, 2023
@Calinou Calinou added the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Sep 18, 2023
@aaronfranke aaronfranke changed the title [Meta] Remove lgtm.yml since LGTM is now replaced by Github Code Scanning. Remove lgtm.yml since LGTM is now replaced by Github Code Scanning Sep 18, 2023
@AThousandShips AThousandShips modified the milestones: 4.2, 4.3 Oct 26, 2023
Copy link
Contributor

@YuriSizov YuriSizov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we should've done this alongside #66714.

If we want to use code scanning, we need to create a workflow for it with GitHub Actions. But it looks like the only reason we have a config is because we've had the badge and it wasn't building correctly (#41739). So for now, removing it seems fine.

PS. Should probably cherry-pick into the 4.0 branch as well. 3.x seems to be unaffected (we had a badge there, but not the config).

@YuriSizov YuriSizov added the cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release label Jan 23, 2024
@YuriSizov YuriSizov merged commit 74c32fa into godotengine:master Jan 23, 2024
15 checks passed
@YuriSizov
Copy link
Contributor

Thanks!

@YuriSizov
Copy link
Contributor

Cherry-picked for 4.2.2.
Cherry-picked for 4.1.4.
Cherry-picked for 4.0.5 (well, into the 4.0 branch, we don't have plans for 4.0.5 at this time).

@YuriSizov YuriSizov added topic:buildsystem and removed cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release labels Jan 23, 2024
@mrbbbaixue mrbbbaixue deleted the remove-lgtm branch January 23, 2024 15:47
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.

4 participants