errors.blank_password = Şifre gereklidir.
errors.password_length = Şifre en az {0} karakter uzunluğunda olmalıdır.
errors.password_no_uppercase = Şifre en az bir büyük harf içermelidir.
errors.password_no_lowercase = Şifre en az bir küçük harf içermelidir.
errors.password_no_digit = Şifre en az bir rakam içermelidir.
errors.password_no_special_char = Şifre en az bir özel karakter içermelidir.

        run: |
          set -eu
          git config --global user.email "******@****.***"
          git config --global user.name "GitHub Action"

          git reset origin/master --hard

          ./gradlew wrapper --gradle-version=nightly
          ./gradlew wrapper

          if ! git diff --quiet; then
            ./gradlew -v
            VERSION=$(./gradlew -v | grep "Gradle" | cut -d' ' -f2)

We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:

* They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made
* They are not synced with the code to reflect the eventual solution that is committed
* Google Docs is not a "code-oriented" tool, like Markdown can be

labels.searchlog_log_type_search_count_day=Jumlah Pencarian/Hari
labels.searchlog_log_type_search_user_hour=Jumlah Pengguna/Jam
labels.searchlog_log_type_search_user_day=Jumlah Pengguna/Hari
labels.searchlog_log_type_search_reqtimeavg_hour=Waktu Rata-rata Permintaan/Jam
labels.searchlog_log_type_search_reqtimeavg_day=Waktu Rata-rata Permintaan/Hari
labels.searchlog_log_type_click_count=Jumlah Klik

"berori", "beroriek", "beste", "bezala", "da", "dago", "dira", "ditu", "du", "dute", "edo", "egin", "ere", "eta", "eurak", "ez", "gainera", "gu", "gutxi", "guzti", "haiei", "haiek", "haietan", "hainbeste", "hala", "han", "handik", "hango", "hara", "hari", "hark", "hartan", "hau", "hauei", "hauek", "hauetan", "hemen", "hemendik", "hemengo", "hi", "hona", "honek", "honela", "honetan", "honi", "hor", "hori", "horiei", "horiek", "horietan", "horko", "horra", "horrek", "horrela", "horretan", "horri", "hortik",...

"berori", "beroriek", "beste", "bezala", "da", "dago", "dira", "ditu", "du", "dute", "edo", "egin", "ere", "eta", "eurak", "ez", "gainera", "gu", "gutxi", "guzti", "haiei", "haiek", "haietan", "hainbeste", "hala", "han", "handik", "hango", "hara", "hari", "hark", "hartan", "hau", "hauei", "hauek", "hauetan", "hemen", "hemendik", "hemengo", "hi", "hona", "honek", "honela", "honetan", "honi", "hor", "hori", "horiei", "horiek", "horietan", "horko", "horra", "horrek", "horrela", "horretan", "horri", "hortik",...

            processor.setSearcher(new TestSearcher(100));
            processor.register(new TestSearcher(0)); // Empty searcher
            processor.register(new TestSearcher(50)); // Half-full searcher
            processor.init();

            final List<Map<String, Object>> results = processor.search("*", new TestSearchRequestParams(0, 10, 0), OptionalThing.empty());
            assertNotNull(results);

The Gradle codebase has evolved over time and has a mixture of simple getter/setter methods, Provider API and things in between.  It can be hard to follow best practices because Gradle provided types are reused in unexpected ways and extended by third party plugins.