-
Notifications
You must be signed in to change notification settings - Fork 624
Include Kotlin directories in the Dackka plugin #4847
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
Conversation
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. Add the 'main-merge-ack' label to your PR to confirm merging into the main branch is intended. |
Size Report 1Affected ProductsNo changes between base commit (26de539) and merge commit (755c1f0).Test Logs |
Coverage Report 1Affected Products
Test Logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! We haven't had any kotlin
directories yet, so this never came up. Our other kotlin files lived under the java
directory :')
Include Kotlin directories in the Dackka plugin.
The
generateDackkaDocumentation
task was not outputting anything onfirebase-sessions
because it was ignoring themain/kotlin/
src dir, it only looked atmain/java/
before. This was causing some workflows to fail on every PR since sessions is entirely written in Kotlin.