Things to sync

This is a (probably incomplete) list of configs and files that are still not synced but could be. To be done one by one, most likely, as adaptations will be needed to make things common between al projects. Challenges for each thing are also detailed here.

This list is up for discussion, not all of this needs to be synced.

Config files

• .codecov.yml
• detekt.yml
• dependabot.yml #35
  • unless we replace dependabot with Renovate in all repos. That may fix https://github.com/nextcloud/android-common/issues/21
• drone config? (only talk + files)
  • currently very different between talk and files
• .editorconfig
• Fastlane stuff
  - Will need to have differences for different apps

Gradle configs

We can either do .gradle files here, sync them and apply them from our projects, or publish them as Gradle plugins on android-common

• Task to install git hooks
• Spotbugs configuration
• JaCoCo configuration
• Spotless config
• Detekt config
• shot/screenshots config

Github Workflows

• analysis
  • uses scripts that should be synced too
  • maybe we should split this into several workflows, one for each analysis step, with less complicated scripts
• assemble
  • assemble logic is common, but not flavors. Talk doesn't have Huawei, android-library and android-common don't have a flavor dimension to begin with (only debug and release)
• autoApproveDependabot (or renovate, if we switch to it) #43
• check
  • again, some repos have checks that others don't
  • talk doesn't use spotless but all others do
  • library and common include the lint check, while talk and files do it in analysis step instead
• gradle-wrapper-validation.yml
• qa.yml
  • files has an extra step to install NDK. we can install it anyway on Talk, or handle it some other way
• scorecards.yml?

Scripts

• git hooks
  • need to make them flexible as not all checks are available in all projects
• analysis-related
  • some may be obsolete if analysis is cleaned up and split into parts
• screenshots-related
• utilities
  • wait_for_emulator, wait_for_server

Start by comparing the listed configuration files, Gradle configurations, GitHub workflows, and scripts across the Android projects. First resolve which items are actually in scope, since the issue is an incomplete discussion list and notes project-specific differences. Done means the selected items are agreed on and synchronized without removing required per-project adaptations; no test command is named.