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 Android Lint checks to CI #1742

Open
BenHenning opened this issue Aug 29, 2020 · 2 comments
Open

Add Android Lint checks to CI #1742

BenHenning opened this issue Aug 29, 2020 · 2 comments
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Work: High It's not clear what the solution is. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

Add support for Android Lint in CI. This is currently supported in Gradle, but some custom work will probably be needed for Bazel: bazelbuild/rules_android#321.

I believe Android Lint checks work correctly with Kotlin, but it's not clear if all checks work.

@BenHenning BenHenning added Type: Improvement Priority: Nice-to-have This work item is nice to have for its milestone. labels Aug 29, 2020
@anandwana001
Copy link
Contributor

Oh Great, As we are planning to add Android Lint tool we can block the add XML lint issue on this issue.

@soamOne
Copy link
Contributor

soamOne commented Jan 4, 2021

Hey @BenHenning @anandwana001 can I work on this?

@BenHenning BenHenning added this to the Beta MR2 milestone Jun 11, 2022
@Broppia Broppia added issue_type_infrastructure Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 29, 2022
@BenHenning BenHenning added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Z-ibt Temporary label for Ben to keep track of issues he's triaged. and removed Impact: Low Low perceived user impact (e.g. edge cases). labels Sep 16, 2022
@BenHenning BenHenning removed this from the Beta MR2 milestone Sep 16, 2022
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed issue_type_infrastructure labels Mar 28, 2023
@MohitGupta121 MohitGupta121 added the Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. label Jun 16, 2023
@MohitGupta121 MohitGupta121 added Work: High It's not clear what the solution is. and removed Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. labels Jun 27, 2023
@seanlip seanlip removed the Priority: Nice-to-have This work item is nice to have for its milestone. label Jun 28, 2023
@adhiamboperes adhiamboperes added this to the 1.0 Global availability milestone Feb 12, 2024
@seanlip seanlip removed this from the 1.0 Global availability milestone Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Work: High It's not clear what the solution is. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

No branches or pull requests

7 participants