{"id":45702,"date":"2026-11-15T09:07:54","date_gmt":"2026-11-15T06:07:54","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/"},"modified":"2026-11-15T09:07:54","modified_gmt":"2026-11-15T06:07:54","slug":"github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/","title":{"rendered":"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131"},"content":{"rendered":"<h2>GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131<\/h2>\n<p>GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zda tekrar eden YAML kodlar\u0131ndan s\u0131k\u0131ld\u0131n\u0131z m\u0131? S\u00fcrekli ayn\u0131 ad\u0131mlar\u0131, ortam de\u011fi\u015fkenlerini veya yap\u0131land\u0131rmalar\u0131 kopyalay\u0131p yap\u0131\u015ft\u0131rmak, hem zaman kayb\u0131na yol a\u00e7ar hem de i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n s\u00fcrd\u00fcr\u00fclebilirli\u011fini olumsuz etkiler. Bu makalede, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 daha temiz, s\u00fcrd\u00fcr\u00fclebilir ve y\u00f6netilebilir hale getirmek i\u00e7in YAML \u00e7apalar\u0131n\u0131 (anchors), takma adlar\u0131 (aliases) ve birle\u015fme anahtar\u0131n\u0131 (merge key) nas\u0131l kullanaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m ke\u015ffedeceksiniz. Tekrar eden yap\u0131land\u0131rmalara elveda deyin ve CI\/CD (S\u00fcrekli Entegrasyon\/S\u00fcrekli Teslimat) s\u00fcre\u00e7lerinizi optimize edin.<\/p>\n<p>Modern yaz\u0131l\u0131m geli\u015ftirme pratiklerinde, otomasyonun yeri tart\u0131\u015f\u0131lamaz. GitHub Actions, bu otomasyonu do\u011frudan geli\u015ftirme platformunuza entegre ederek, kodunuzu her commit&#8217;te derlemenize, test etmenize ve da\u011f\u0131tman\u0131za olanak tan\u0131r. Ancak, projeler b\u00fcy\u00fcd\u00fck\u00e7e ve i\u015f ak\u0131\u015flar\u0131 karma\u015f\u0131kla\u015ft\u0131k\u00e7a, YAML dosyalar\u0131nda tekrar eden bloklar ka\u00e7\u0131n\u0131lmaz hale gelir. Bu durum, \u00f6zellikle birden fazla ortam (geli\u015ftirme, test, \u00fcretim) veya farkl\u0131 platformlar (Linux, macOS, Windows) i\u00e7in benzer ad\u0131mlar\u0131n tan\u0131mlanmas\u0131 gerekti\u011finde belirginle\u015fir. \u0130\u015fte tam bu noktada, YAML&#8217;in sundu\u011fu g\u00fc\u00e7l\u00fc \u00f6zellikler olan \u00e7apalar, takma adlar ve birle\u015fme anahtar\u0131 devreye girer. Bu ara\u00e7lar sayesinde, bir kez tan\u0131mlad\u0131\u011f\u0131n\u0131z yap\u0131land\u0131rmalar\u0131 birden fazla yerde yeniden kullanabilir, b\u00f6ylece kod tekrar\u0131n\u0131 (DRY &#8211; Don&#8217;t Repeat Yourself prensibi) en aza indirebilirsiniz. Bu makale boyunca, bu kavramlar\u0131 temelden alarak, ger\u00e7ek d\u00fcnya senaryolar\u0131yla peki\u015ftirecek ve GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 bir sonraki seviyeye ta\u015f\u0131yacak pratik bilgiler sunaca\u011f\u0131z.<\/p>\n<h2>GitHub Actions YAML&#8217;e H\u0131zl\u0131 Bir Bak\u0131\u015f ve Tekrar Eden Kod Sorunu<\/h2>\n<p>GitHub Actions, do\u011frudan GitHub deponuzda yaz\u0131l\u0131m geli\u015ftirme i\u015f ak\u0131\u015flar\u0131n\u0131 otomatikle\u015ftirmenizi sa\u011flayan g\u00fc\u00e7l\u00fc bir CI\/CD platformudur. Kodunuzu derlemek, test etmek, paketlemek, da\u011f\u0131tmak ve hatta projelerinizle ilgili bildirimler g\u00f6ndermek gibi bir\u00e7ok g\u00f6revi otomatikle\u015ftirebilirsiniz. Bu otomasyon s\u00fcre\u00e7leri, genellikle deponuzun k\u00f6k dizinindeki <code>.github\/workflows<\/code> klas\u00f6r\u00fcnde bulunan YAML (Yet Another Markup Language) dosyalar\u0131 arac\u0131l\u0131\u011f\u0131yla tan\u0131mlan\u0131r.<\/p>\n<p>YAML, insan taraf\u0131ndan kolayca okunabilir ve yaz\u0131labilir bir veri serile\u015ftirme standard\u0131d\u0131r. Yap\u0131land\u0131rma dosyalar\u0131, g\u00fcnl\u00fck dosyalar\u0131, s\u00fcre\u00e7ler aras\u0131 mesajla\u015fma gibi bir\u00e7ok alanda yayg\u0131n olarak kullan\u0131l\u0131r. GitHub Actions ba\u011flam\u0131nda, her bir YAML dosyas\u0131 bir &#8220;i\u015f ak\u0131\u015f\u0131&#8221;n\u0131 (workflow) temsil eder ve bu i\u015f ak\u0131\u015flar\u0131, bir veya daha fazla &#8220;i\u015f&#8221;ten (job) olu\u015fur. Her i\u015f ise belirli bir s\u0131raya g\u00f6re y\u00fcr\u00fct\u00fclen &#8220;ad\u0131m&#8221;lardan (step) meydana gelir. Bu hiyerar\u015fik yap\u0131, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n mant\u0131\u011f\u0131n\u0131 a\u00e7\u0131k\u00e7a ifade etmenizi sa\u011flar.<\/p>\n<p>Ancak, bu esnekli\u011fin bir bedeli vard\u0131r: tekrar eden kod. \u00d6zellikle b\u00fcy\u00fck projelerde veya birden fazla benzer i\u015f ak\u0131\u015f\u0131 tan\u0131mlaman\u0131z gerekti\u011finde, kendinizi s\u00fcrekli ayn\u0131 kod bloklar\u0131n\u0131 kopyalay\u0131p yap\u0131\u015ft\u0131r\u0131rken bulabilirsiniz. \u00d6rne\u011fin, t\u00fcm i\u015flerinizde belirli ortam de\u011fi\u015fkenlerini tan\u0131mlaman\u0131z, ayn\u0131 ba\u011f\u0131ml\u0131l\u0131klar\u0131 y\u00fcklemeniz veya benzer test komutlar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rman\u0131z gerekebilir. Bu durum, a\u015fa\u011f\u0131daki sorunlara yol a\u00e7ar:<\/p>\n<ul>\n<li><strong>S\u00fcrd\u00fcr\u00fclebilirlik Zorluklar\u0131:<\/strong> Bir yap\u0131land\u0131rmay\u0131 de\u011fi\u015ftirmek istedi\u011finizde, bu de\u011fi\u015fikli\u011fi kopyalad\u0131\u011f\u0131n\u0131z her yere manuel olarak uygulaman\u0131z gerekir. Bu, hata yapma olas\u0131l\u0131\u011f\u0131n\u0131 art\u0131r\u0131r ve zaman al\u0131c\u0131d\u0131r.<\/li>\n<li><strong>Okunabilirlik Azalmas\u0131:<\/strong> Tekrar eden kod bloklar\u0131, i\u015f ak\u0131\u015f\u0131 dosyan\u0131z\u0131n boyutunu gereksiz yere art\u0131r\u0131r ve genel okunabilirli\u011fi d\u00fc\u015f\u00fcr\u00fcr. Bu da yeni bir geli\u015ftiricinin i\u015f ak\u0131\u015f\u0131n\u0131 anlamas\u0131n\u0131 zorla\u015ft\u0131r\u0131r.<\/li>\n<li><strong>Hata Potansiyeli:<\/strong> Kopyala-yap\u0131\u015ft\u0131r i\u015flemleri s\u0131ras\u0131nda yap\u0131lan k\u00fc\u00e7\u00fck bir hata, t\u00fcm i\u015f ak\u0131\u015f\u0131n\u0131 etkileyebilir ve sorunlar\u0131n tespitini zorla\u015ft\u0131rabilir. \u00d6rne\u011fin, bir ortam de\u011fi\u015fkeni ad\u0131n\u0131 yanl\u0131\u015f yazmak veya bir komutta k\u00fc\u00e7\u00fck bir tipografik hata yapmak, beklenmedik davran\u0131\u015flara yol a\u00e7abilir.<\/li>\n<li><strong>Verimsizlik:<\/strong> Gereksiz yere uzun ve tekrar eden dosyalar, s\u00fcr\u00fcm kontrol sistemlerinde (Git gibi) daha fazla yer kaplar ve de\u011fi\u015fiklikleri incelemeyi (code review) zorla\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\n<p>Bu sorunlar\u0131 a\u015fmak i\u00e7in YAML, \u00e7apalar (anchors) ve takma adlar (aliases) gibi mekanizmalar sunar. Bu \u00f6zellikler, belirli bir YAML blo\u011funu i\u015faretlemenize ve daha sonra bu blo\u011fu i\u015f ak\u0131\u015f\u0131n\u0131z\u0131n farkl\u0131 yerlerinde yeniden kullanman\u0131za olanak tan\u0131r. B\u00f6ylece, ortak yap\u0131land\u0131rma par\u00e7alar\u0131n\u0131 bir kez tan\u0131mlay\u0131p bir\u00e7ok yerde kullanabilir, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 daha mod\u00fcler ve y\u00f6netilebilir hale getirebilirsiniz. Bu, \u00f6zellikle karma\u015f\u0131k CI\/CD boru hatlar\u0131nda tutarl\u0131l\u0131k sa\u011flamak ve geli\u015ftirme h\u0131z\u0131n\u0131 art\u0131rmak i\u00e7in kritik \u00f6neme sahiptir. Bir sonraki b\u00f6l\u00fcmde, bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve GitHub Actions ba\u011flam\u0131nda nas\u0131l uygulanaca\u011f\u0131n\u0131 detayl\u0131ca inceleyece\u011fiz.<\/p>\n<h2>YAML \u00c7apalar\u0131 (Anchors) ve Takma Adlar (Aliases) Nedir ve Nas\u0131l Kullan\u0131l\u0131r?<\/h2>\n<p>YAML \u00e7apalar\u0131 ve takma adlar, YAML dosyalar\u0131nda tekrar eden veri yap\u0131lar\u0131n\u0131 ortadan kald\u0131rmak i\u00e7in kullan\u0131lan temel mekanizmalard\u0131r. Temel olarak, bir blo\u011fu bir kez tan\u0131mlay\u0131p ona bir isim (\u00e7apa) verirsiniz ve daha sonra bu ismi (takma ad) kullanarak o blo\u011fu farkl\u0131 yerlerde referans g\u00f6sterirsiniz. Bu sayede, ayn\u0131 i\u00e7eri\u011fi birden fazla kez yazmaktan kurtulur, YAML dosyalar\u0131n\u0131z\u0131n daha k\u0131sa, daha temiz ve daha s\u00fcrd\u00fcr\u00fclebilir olmas\u0131n\u0131 sa\u011flars\u0131n\u0131z.<\/p>\n<h3>\u00c7apa (Anchor) Nedir?<\/h3>\n<p>Bir \u00e7apa, bir YAML d\u00fc\u011f\u00fcm\u00fcn\u00fc (node) i\u015faretlemek i\u00e7in kullan\u0131l\u0131r. Bu d\u00fc\u011f\u00fcm bir harita (mapping), bir liste (sequence) veya bir skaler de\u011fer (scalar) olabilir. \u00c7apa, <code>&amp;<\/code> sembol\u00fc ile tan\u0131mlan\u0131r ve hemen ard\u0131ndan bir isim gelir. \u00d6rne\u011fin, <code>&amp;ortak_ayarlar<\/code> \u015feklinde bir \u00e7apa tan\u0131mlayabilirsiniz. Bu \u00e7apa, i\u015faretledi\u011fi veri blo\u011funa bir referans noktas\u0131 sa\u011flar.<\/p>\n<h3>Takma Ad (Alias) Nedir?<\/h3>\n<p>Bir takma ad, daha \u00f6nce tan\u0131mlanm\u0131\u015f bir \u00e7apay\u0131 referans g\u00f6stermek i\u00e7in kullan\u0131l\u0131r. Takma ad, <code>*<\/code> sembol\u00fc ile tan\u0131mlan\u0131r ve hemen ard\u0131ndan \u00e7apaya verdi\u011finiz isim gelir. \u00d6rne\u011fin, <code>*ortak_ayarlar<\/code> \u015feklinde bir takma ad kullanarak, <code>&amp;ortak_ayarlar<\/code> \u00e7apas\u0131yla i\u015faretlenmi\u015f veri blo\u011funu oldu\u011fu gibi dahil edebilirsiniz. YAML ayr\u0131\u015ft\u0131r\u0131c\u0131s\u0131 (parser), takma ad\u0131 g\u00f6rd\u00fc\u011f\u00fcnde, i\u015faret etti\u011fi \u00e7apan\u0131n i\u00e7eri\u011fini o noktaya kopyalar.<\/p>\n<h3>Basit Bir \u00d6rnek: Ortak Ortam De\u011fi\u015fkenlerini Yeniden Kullanma<\/h3>\n<p>Hayal edin ki, t\u00fcm i\u015flerinizde belirli bir <code>WORKING_DIRECTORY<\/code> ve <code>NODE_VERSION<\/code> kullanman\u0131z gerekiyor. Bu de\u011ferleri her i\u015fte tekrar tekrar tan\u0131mlamak yerine, bir \u00e7apa kullanarak bunlar\u0131 bir kez tan\u0131mlayabilir ve sonra takma adlarla referans g\u00f6sterebilirsiniz. \u0130\u015fte bir \u00f6rnek:<\/p>\n<div class=\"code-container\">\n<pre><code>\njobs:\n  # Ortak ayarlar\u0131 tan\u0131mlayan bir \u00e7apa\n  &amp;ortak_vars:\n    env:\n      WORKING_DIRECTORY: '.\/app'\n      NODE_VERSION: '18'\n\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Kodu D\u0131\u015far\u0131 \u00c7ek\n        uses: actions\/checkout@v4\n      - name: Ortam De\u011fi\u015fkenlerini Ayarla ve Node.js Kur\n        uses: actions\/setup-node@v4\n        with:\n          node-version: *ortak_vars.env.NODE_VERSION # Do\u011frudan skaler de\u011feri referans alabiliriz\n      - name: Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Y\u00fckle\n        run: npm install\n        working-directory: *ortak_vars.env.WORKING_DIRECTORY # Yine skaler de\u011feri referans al\u0131yoruz\n      - name: Uygulamay\u0131 Olu\u015ftur\n        run: npm run build\n        working-directory: *ortak_vars.env.WORKING_DIRECTORY\n\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Kodu D\u0131\u015far\u0131 \u00c7ek\n        uses: actions\/checkout@v4\n      - name: Ortam De\u011fi\u015fkenlerini Ayarla ve Node.js Kur\n        uses: actions\/setup-node@v4\n        with:\n          node-version: *ortak_vars.env.NODE_VERSION\n      - name: Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Y\u00fckle\n        run: npm install\n        working-directory: *ortak_vars.env.WORKING_DIRECTORY\n      - name: Testleri \u00c7al\u0131\u015ft\u0131r\n        run: npm test\n        working-directory: *ortak_vars.env.WORKING_DIRECTORY\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Yukar\u0131daki \u00f6rnekte, <code>&amp;ortak_vars<\/code> ad\u0131nda bir \u00e7apa tan\u0131mlad\u0131k. Bu \u00e7apa, <code>env<\/code> anahtar\u0131n\u0131n alt\u0131nda <code>WORKING_DIRECTORY<\/code> ve <code>NODE_VERSION<\/code> de\u011ferlerini i\u00e7eriyor. Daha sonra, <code>build<\/code> ve <code>test<\/code> i\u015flerindeki ad\u0131mlarda, bu de\u011ferleri <code>*ortak_vars.env.NODE_VERSION<\/code> ve <code>*ortak_vars.env.WORKING_DIRECTORY<\/code> \u015feklinde referans g\u00f6sterdik. Bu yakla\u015f\u0131m, \u00f6zellikle birden fazla i\u015f veya ad\u0131mda ayn\u0131 skaler de\u011ferleri kullanman\u0131z gerekti\u011finde olduk\u00e7a faydal\u0131d\u0131r. Ancak, t\u00fcm bir haritay\u0131 veya listeyi dahil etmek istedi\u011finizde, birle\u015fme anahtar\u0131 (merge key) devreye girer.<\/p>\n<p>\u00c7apalar ve takma adlar, YAML&#8217;in temel yap\u0131s\u0131n\u0131 kullanarak veri tekrar\u0131n\u0131 \u00f6nlemenin zarif bir yolunu sunar. Bu \u00f6zellikler, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n daha okunabilir, daha y\u00f6netilebilir ve daha az hata yapmaya a\u00e7\u0131k olmas\u0131n\u0131 sa\u011flar. \u00d6zellikle b\u00fcy\u00fck ve karma\u015f\u0131k GitHub Actions i\u015f ak\u0131\u015flar\u0131nda, bu basit ama g\u00fc\u00e7l\u00fc ara\u00e7lar, geli\u015ftirme s\u00fcrecinizi \u00f6nemli \u00f6l\u00e7\u00fcde h\u0131zland\u0131rabilir ve bak\u0131m maliyetlerini d\u00fc\u015f\u00fcrebilir. \u015eimdi, \u00e7apalar ve takma adlarla birlikte s\u0131kl\u0131kla kullan\u0131lan birle\u015fme anahtar\u0131n\u0131n ne oldu\u011funu ve nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 inceleyelim.<\/p>\n<h2>Birle\u015fme Anahtar\u0131 (Merge Key) <code>&lt;&lt;:<\/code>: Derinlemesine Bir Bak\u0131\u015f<\/h2>\n<p>YAML \u00e7apalar\u0131 ve takma adlar, bir blo\u011fu referans g\u00f6stermek i\u00e7in harika ara\u00e7lard\u0131r, ancak bazen bir haritan\u0131n (mapping) i\u00e7eri\u011fini ba\u015fka bir haritaya &#8220;birle\u015ftirmek&#8221; isteyebilirsiniz. Yani, bir blo\u011fun t\u00fcm anahtar-de\u011fer \u00e7iftlerini al\u0131p, ba\u015fka bir blo\u011fun anahtar-de\u011fer \u00e7iftleriyle birle\u015ftirmek. \u0130\u015fte bu noktada, birle\u015fme anahtar\u0131 (merge key) olan <code>&lt;&lt;:<\/code> devreye girer. Bu \u00f6zel anahtar, YAML spesifikasyonunun bir par\u00e7as\u0131 de\u011fildir, ancak bir\u00e7ok YAML i\u015flemcisinde (parser) ve \u00f6zellikle GitHub Actions&#8217;ta yayg\u0131n olarak desteklenen bir uzant\u0131d\u0131r.<\/p>\n<h3>Birle\u015fme Anahtar\u0131 Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/h3>\n<p><code>&lt;&lt;:<\/code> anahtar\u0131, bir harita (map) i\u00e7inde kullan\u0131ld\u0131\u011f\u0131nda, belirtilen takma ad\u0131n (alias) i\u015faret etti\u011fi haritan\u0131n i\u00e7eri\u011fini mevcut haritaya dahil eder. E\u011fer birle\u015fen haritalarda ayn\u0131 anahtarlar varsa, birle\u015fme anahtar\u0131ndan sonra tan\u0131mlanan anahtarlar, \u00f6nceki de\u011ferleri ge\u00e7ersiz k\u0131lar (override eder). Bu &#8220;son giren kazan\u0131r&#8221; (last-one-wins) kural\u0131, esneklik ve \u00f6zelle\u015ftirme imkan\u0131 sunar.<\/p>\n<h3>\u00d6rnek: Ortak Ad\u0131mlar\u0131 ve Varsay\u0131lanlar\u0131 Birle\u015ftirme<\/h3>\n<p>Bir\u00e7ok i\u015f ak\u0131\u015f\u0131n\u0131zda ba\u015flang\u0131\u00e7ta ayn\u0131 ad\u0131mlar\u0131 (\u00f6rne\u011fin, kodu d\u0131\u015far\u0131 \u00e7ekme, ba\u011f\u0131ml\u0131l\u0131klar\u0131 y\u00fckleme) ve ayn\u0131 varsay\u0131lan yap\u0131land\u0131rmalar\u0131 (\u00f6rne\u011fin, kabuk tipi, \u00e7al\u0131\u015fma dizini) kullanman\u0131z gerekebilir. Bu senaryo, birle\u015fme anahtar\u0131n\u0131n g\u00fcc\u00fcn\u00fc g\u00f6stermek i\u00e7in idealdir.<\/p>\n<div class=\"code-container\">\n<pre><code>\ndefaults:\n  run:\n    shell: bash\n    working-directory: '.\/app'\n\ncommon_setup_steps: &amp;common_setup # Ortak kurulum ad\u0131mlar\u0131n\u0131 tan\u0131mlayan \u00e7apa\n  - uses: actions\/checkout@v4\n  - name: Node.js Kurulumu\n    uses: actions\/setup-node@v4\n    with:\n      node-version: '18'\n  - name: Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Y\u00fckle\n    run: npm install\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      &lt;&lt;: *common_setup # common_setup \u00e7apas\u0131 ile tan\u0131mlanan ad\u0131mlar\u0131 dahil et\n      - name: Uygulamay\u0131 Olu\u015ftur\n        run: npm run build\n\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      &lt;&lt;: *common_setup # common_setup \u00e7apas\u0131 ile tan\u0131mlanan ad\u0131mlar\u0131 dahil et\n      - name: Testleri \u00c7al\u0131\u015ft\u0131r\n        run: npm test --coverage\n\n  deploy_production:\n    runs-on: ubuntu-latest\n    steps:\n      &lt;&lt;: *common_setup # common_setup \u00e7apas\u0131 ile tan\u0131mlanan ad\u0131mlar\u0131 dahil et\n      - name: \u00dcretim Ortam\u0131na Da\u011f\u0131t\n        run: npm run deploy:prod\n        env:\n          NODE_ENV: production # Bu i\u015fe \u00f6zel ortam de\u011fi\u015fkeni\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Yukar\u0131daki \u00f6rnekte, <code>common_setup_steps<\/code> ad\u0131nda bir \u00e7apa tan\u0131mlad\u0131k. Bu \u00e7apa, bir dizi ortak kurulum ad\u0131m\u0131n\u0131 i\u00e7eriyor. Daha sonra, <code>build<\/code>, <code>test<\/code> ve <code>deploy_production<\/code> i\u015flerinde, <code>steps<\/code> anahtar\u0131n\u0131n alt\u0131nda <code>&lt;&lt;: *common_setup<\/code> kullanarak bu ad\u0131mlar\u0131 dahil ettik. Bu sayede, her i\u015f i\u00e7in ayr\u0131 ayr\u0131 <code>checkout<\/code>, <code>setup-node<\/code> ve <code>npm install<\/code> ad\u0131mlar\u0131n\u0131 yazmaktan kurtulduk.<\/p>\n<h3>Ge\u00e7ersiz K\u0131lma (Overriding) Davran\u0131\u015f\u0131<\/h3>\n<p>Birle\u015fme anahtar\u0131n\u0131n en g\u00fc\u00e7l\u00fc yanlar\u0131ndan biri, dahil edilen haritalar\u0131n anahtarlar\u0131n\u0131 ge\u00e7ersiz k\u0131labilme yetene\u011fidir. E\u011fer birle\u015fme anahtar\u0131 ile dahil etti\u011finiz bir haritada ve mevcut haritan\u0131zda ayn\u0131 anahtarlar varsa, mevcut haritan\u0131zdaki anahtar\u0131n de\u011feri, dahil edilen haritadaki de\u011feri ge\u00e7ersiz k\u0131lar. Bu, varsay\u0131lan yap\u0131land\u0131rmalar\u0131 tan\u0131mlay\u0131p, belirli durumlarda bunlar\u0131 \u00f6zelle\u015ftirmenize olanak tan\u0131r.<\/p>\n<div class=\"code-container\">\n<pre><code>\ndefault_job_config: &amp;default_config\n  runs-on: ubuntu-latest\n  env:\n    BUILD_ENV: development\n    LOG_LEVEL: info\n\njobs:\n  build_dev:\n    &lt;&lt;: *default_config # Varsay\u0131lan yap\u0131land\u0131rmay\u0131 dahil et\n    steps:\n      - name: Geli\u015ftirme Ortam\u0131 Olu\u015ftur\n        run: echo \"Building for development with $BUILD_ENV\"\n\n  build_prod:\n    &lt;&lt;: *default_config # Varsay\u0131lan yap\u0131land\u0131rmay\u0131 dahil et\n    env:\n      BUILD_ENV: production # BUILD_ENV'yi ge\u00e7ersiz k\u0131l\n      LOG_LEVEL: warn # LOG_LEVEL'i ge\u00e7ersiz k\u0131l\n    steps:\n      - name: \u00dcretim Ortam\u0131 Olu\u015ftur\n        run: echo \"Building for production with $BUILD_ENV and $LOG_LEVEL\"\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu \u00f6rnekte, <code>default_job_config<\/code> \u00e7apas\u0131, <code>BUILD_ENV<\/code> ve <code>LOG_LEVEL<\/code> i\u00e7in varsay\u0131lan de\u011ferler tan\u0131ml\u0131yor. <code>build_dev<\/code> i\u015fi bu varsay\u0131lanlar\u0131 oldu\u011fu gibi kullan\u0131rken, <code>build_prod<\/code> i\u015fi <code>env<\/code> blo\u011funu yeniden tan\u0131mlayarak <code>BUILD_ENV<\/code> ve <code>LOG_LEVEL<\/code> de\u011ferlerini ge\u00e7ersiz k\u0131l\u0131yor. B\u00f6ylece, <code>build_prod<\/code> i\u015fi i\u00e7in <code>BUILD_ENV<\/code> <code>production<\/code> ve <code>LOG_LEVEL<\/code> <code>warn<\/code> olacakt\u0131r. Bu esneklik, farkl\u0131 ortamlar veya \u00f6zel durumlar i\u00e7in i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 kolayca uyarlaman\u0131z\u0131 sa\u011flar.<\/p>\n<p>\u00d6zetle, birle\u015fme anahtar\u0131 <code>&lt;&lt;:<\/code>, YAML \u00e7apalar\u0131 ve takma adlarla birlikte kullan\u0131ld\u0131\u011f\u0131nda, karma\u015f\u0131k yap\u0131land\u0131rmalar\u0131 mod\u00fcler hale getirmenin ve tekrar eden koddan ka\u00e7\u0131nman\u0131n \u00e7ok g\u00fc\u00e7l\u00fc bir yolunu sunar. Bu, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n bak\u0131m\u0131n\u0131 kolayla\u015ft\u0131r\u0131r, hatalar\u0131 azalt\u0131r ve genel olarak CI\/CD s\u00fcre\u00e7lerinizin verimlili\u011fini art\u0131r\u0131r. Bir sonraki b\u00f6l\u00fcmde, bu kavramlar\u0131 ger\u00e7ek d\u00fcnya senaryolar\u0131nda nas\u0131l uygulayabilece\u011fimize dair vaka analizleri sunaca\u011f\u0131z.<\/p>\n<h2>Ger\u00e7ek D\u00fcnya Senaryolar\u0131: Tekrar Eden \u0130\u015f Ak\u0131\u015flar\u0131n\u0131 Optimize Etme<\/h2>\n<p>\u015eimdiye kadar YAML \u00e7apalar\u0131, takma adlar ve birle\u015fme anahtar\u0131n\u0131n temel prensiplerini ve nas\u0131l \u00e7al\u0131\u015ft\u0131klar\u0131n\u0131 inceledik. Ancak bu kavramlar\u0131n ger\u00e7ek bir projede nas\u0131l de\u011fer yaratt\u0131\u011f\u0131n\u0131 g\u00f6rmek, onlar\u0131n g\u00fcc\u00fcn\u00fc tam olarak anlamam\u0131z\u0131 sa\u011flar. \u0130\u015fte GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zdaki tekrar\u0131 azaltmak ve verimlili\u011fi art\u0131rmak i\u00e7in bu teknikleri kullanabilece\u011finiz birka\u00e7 ger\u00e7ek d\u00fcnya senaryosu.<\/p>\n<h3>Vaka Analizi 1: Matris \u0130\u015fleri \u0130\u00e7in Ortak Kurulum Ad\u0131mlar\u0131n\u0131 Yeniden Kullanma<\/h3>\n<p>Bir yaz\u0131l\u0131m projesinin, farkl\u0131 Node.js s\u00fcr\u00fcmleri ve i\u015fletim sistemleri kombinasyonlar\u0131 \u00fczerinde test edilmesi gerekti\u011fini varsayal\u0131m. GitHub Actions&#8217;\u0131n matris stratejisi (matrix strategy) bu t\u00fcr senaryolar i\u00e7in idealdir. Ancak, matrisin her bir kombinasyonu i\u00e7in kodu d\u0131\u015far\u0131 \u00e7ekme (checkout), ba\u011f\u0131ml\u0131l\u0131klar\u0131 y\u00fckleme gibi ayn\u0131 ba\u015flang\u0131\u00e7 ad\u0131mlar\u0131n\u0131 tekrar tekrar tan\u0131mlamak, i\u015f ak\u0131\u015f\u0131 dosyas\u0131n\u0131 \u015fi\u015firir ve y\u00f6netimi zorla\u015ft\u0131r\u0131r.<\/p>\n<h4>Problem:<\/h4>\n<p>Her matris kombinasyonu i\u00e7in ayn\u0131 <code>checkout<\/code>, <code>setup-node<\/code> ve <code>npm install<\/code> ad\u0131mlar\u0131n\u0131 tekrar yazmak.<\/p>\n<div class=\"code-container\">\n<pre><code>\njobs:\n  test:\n    runs-on: ${{ matrix.os }}\n    strategy:\n      matrix:\n        os: [ubuntu-latest, windows-latest]\n        node-version: [16, 18, 20]\n    steps:\n      - name: Kodu D\u0131\u015far\u0131 \u00c7ek\n        uses: actions\/checkout@v4\n      - name: Node.js Kurulumu ${{ matrix.node-version }}\n        uses: actions\/setup-node@v4\n        with:\n          node-version: ${{ matrix.node-version }}\n      - name: Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Y\u00fckle\n        run: npm install\n      - name: Testleri \u00c7al\u0131\u015ft\u0131r\n        run: npm test\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu yakla\u015f\u0131m, ad\u0131mlar az oldu\u011funda sorun te\u015fkil etmeyebilir, ancak kurulum ad\u0131mlar\u0131 artt\u0131k\u00e7a YAML dosyan\u0131z\u0131n boyutu h\u0131zla b\u00fcy\u00fcr.<\/p>\n<h4>\u00c7\u00f6z\u00fcm: \u00c7apa ve Birle\u015fme Anahtar\u0131 Kullan\u0131m\u0131<\/h4>\n<p>Ortak kurulum adlar\u0131n\u0131 bir \u00e7apa olarak tan\u0131mlay\u0131p, matris i\u015finde birle\u015fme anahtar\u0131 ile dahil ederek bu tekrar\u0131 \u00f6nleyebiliriz.<\/p>\n<div class=\"code-container\">\n<pre><code>\ncommon_matrix_setup: &amp;matrix_setup_steps\n  - uses: actions\/checkout@v4\n  - name: Node.js Kurulumu ${{ matrix.node-version }}\n    uses: actions\/setup-node@v4\n    with:\n      node-version: ${{ matrix.node-version }}\n  - name: Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Y\u00fckle\n    run: npm install\n\njobs:\n  test:\n    runs-on: ${{ matrix.os }}\n    strategy:\n      matrix:\n        os: [ubuntu-latest, windows-latest]\n        node-version: [16, 18, 20]\n    steps:\n      &lt;&lt;: *matrix_setup_steps # Ortak kurulum ad\u0131mlar\u0131n\u0131 dahil et\n      - name: Testleri \u00c7al\u0131\u015ft\u0131r\n        run: npm test\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu optimize edilmi\u015f versiyonda, <code>common_matrix_setup<\/code> \u00e7apas\u0131 t\u00fcm ortak ad\u0131mlar\u0131 i\u00e7erir. <code>test<\/code> i\u015fi i\u00e7inde, <code>steps<\/code> blo\u011funa <code>&lt;&lt;: *matrix_setup_steps<\/code> ekleyerek bu ad\u0131mlar\u0131 kolayca dahil ederiz. Bu, i\u015f ak\u0131\u015f\u0131 dosyas\u0131n\u0131 \u00e7ok daha okunabilir ve y\u00f6netilebilir hale getirir, ayr\u0131ca gelecekte kurulum ad\u0131mlar\u0131nda bir de\u011fi\u015fiklik yapman\u0131z gerekti\u011finde sadece tek bir yeri g\u00fcncellemeniz yeterli olur.<\/p>\n<h3>Vaka Analizi 2: Farkl\u0131 Ortamlar \u0130\u00e7in Ortak Da\u011f\u0131t\u0131m Ad\u0131mlar\u0131 ve \u00d6zelle\u015ftirmeler<\/h3>\n<p>Bir uygulaman\u0131n geli\u015ftirme (dev), test (staging) ve \u00fcretim (production) ortamlar\u0131na da\u011f\u0131t\u0131lmas\u0131 gerekti\u011fini d\u00fc\u015f\u00fcnelim. Her ortam i\u00e7in da\u011f\u0131t\u0131m ad\u0131mlar\u0131 genellikle benzerdir (\u00f6rne\u011fin, derleme, konteyner olu\u015fturma, bulut sa\u011flay\u0131c\u0131s\u0131na g\u00f6nderme), ancak baz\u0131 ortam de\u011fi\u015fkenleri veya son da\u011f\u0131t\u0131m komutlar\u0131 farkl\u0131l\u0131k g\u00f6sterebilir.<\/p>\n<h4>Problem:<\/h4>\n<p>Her da\u011f\u0131t\u0131m ortam\u0131 i\u00e7in b\u00fcy\u00fck \u00f6l\u00e7\u00fcde ayn\u0131 olan da\u011f\u0131t\u0131m ad\u0131mlar\u0131n\u0131 tekrar tekrar tan\u0131mlamak ve k\u00fc\u00e7\u00fck farkl\u0131l\u0131klar\u0131 y\u00f6netmek.<\/p>\n<div class=\"code-container\">\n<pre><code>\njobs:\n  deploy_dev:\n    runs-on: ubuntu-latest\n    environment: development\n    steps:\n      - uses: actions\/checkout@v4\n      - name: Derle ve Docker \u0130maj\u0131 Olu\u015ftur\n        run: docker build -t myapp:dev .\n      - name: Geli\u015ftirme Ortam\u0131na G\u00f6nder\n        run: docker push myapp:dev && kubectl apply -f k8s\/dev.yaml\n      - name: Geli\u015ftirme Testlerini \u00c7al\u0131\u015ft\u0131r\n        run: echo \"Running dev tests...\"\n\n  deploy_prod:\n    runs-on: ubuntu-latest\n    environment: production\n    steps:\n      - uses: actions\/checkout@v4\n      - name: Derle ve Docker \u0130maj\u0131 Olu\u015ftur\n        run: docker build -t myapp:prod .\n      - name: \u00dcretim Ortam\u0131na G\u00f6nder\n        run: docker push myapp:prod && kubectl apply -f k8s\/prod.yaml\n      - name: \u00dcretim Sonras\u0131 Do\u011frulama\n        run: echo \"Running post-prod validation...\"\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu \u00f6rnekte, <code>deploy_dev<\/code> ve <code>deploy_prod<\/code> i\u015fleri bir\u00e7ok ad\u0131m\u0131 payla\u015f\u0131yor, ancak Docker imaj etiketleri ve Kubernetes yap\u0131land\u0131rma dosyalar\u0131 gibi detaylarda farkl\u0131la\u015f\u0131yorlar. Ayr\u0131ca, her birinin kendine \u00f6zg\u00fc son ad\u0131mlar\u0131 var.<\/p>\n<h4>\u00c7\u00f6z\u00fcm: \u00c7apa, Birle\u015fme Anahtar\u0131 ve Ge\u00e7ersiz K\u0131lma ile Mod\u00fcler Da\u011f\u0131t\u0131m<\/h4>\n<p>Ortak ad\u0131mlar\u0131 bir \u00e7apa olarak tan\u0131mlayabilir, ard\u0131ndan her ortam i\u00e7in \u00f6zelle\u015ftirmelerle bu ad\u0131mlar\u0131 birle\u015ftirebiliriz.<\/p>\n<div class=\"code-container\">\n<pre><code>\ncommon_deploy_steps: &amp;base_deploy_steps\n  - uses: actions\/checkout@v4\n  - name: Derle ve Docker \u0130maj\u0131 Olu\u015ftur\n    run: docker build -t myapp:${{ env.ENV_TAG }} .\n  - name: Ortama G\u00f6nder\n    run: docker push myapp:${{ env.ENV_TAG }} && kubectl apply -f k8s\/${{ env.ENV_TAG }}.yaml\n\njobs:\n  deploy_dev:\n    runs-on: ubuntu-latest\n    environment: development\n    env:\n      ENV_TAG: dev # Bu ortama \u00f6zel etiket\n    steps:\n      &lt;&lt;: *base_deploy_steps # Ortak ad\u0131mlar\u0131 dahil et\n      - name: Geli\u015ftirme Testlerini \u00c7al\u0131\u015ft\u0131r\n        run: echo \"Running dev tests...\"\n\n  deploy_prod:\n    runs-on: ubuntu-latest\n    environment: production\n    env:\n      ENV_TAG: prod # Bu ortama \u00f6zel etiket\n    steps:\n      &lt;&lt;: *base_deploy_steps # Ortak ad\u0131mlar\u0131 dahil et\n      - name: \u00dcretim Sonras\u0131 Do\u011frulama\n        run: echo \"Running post-prod validation...\"\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu iyile\u015ftirilmi\u015f versiyonda, <code>common_deploy_steps<\/code> \u00e7apas\u0131, <code>ENV_TAG<\/code> ortam de\u011fi\u015fkenini kullanarak dinamik olarak imaj etiketlerini ve Kubernetes dosya yollar\u0131n\u0131 belirleyen genel da\u011f\u0131t\u0131m ad\u0131mlar\u0131n\u0131 i\u00e7erir. Her i\u015f, kendi <code>ENV_TAG<\/code>&#8216;ini tan\u0131mlar ve <code>&lt;&lt;: *base_deploy_steps<\/code> ile ortak ad\u0131mlar\u0131 dahil eder. Daha sonra, her i\u015fe \u00f6zg\u00fc ek ad\u0131mlar tan\u0131mlan\u0131r. Bu yakla\u015f\u0131m, da\u011f\u0131t\u0131m i\u015f ak\u0131\u015flar\u0131n\u0131 son derece mod\u00fcler ve kolayca geni\u015fletilebilir hale getirir. Yeni bir ortam eklemek istedi\u011finizde, sadece yeni bir i\u015f tan\u0131mlaman\u0131z ve <code>ENV_TAG<\/code>&#8216;i ayarlaman\u0131z yeterli olur, ortak ad\u0131mlar\u0131 tekrar yazman\u0131za gerek kalmaz.<\/p>\n<p>Bu vaka analizleri, YAML \u00e7apalar\u0131, takma adlar ve birle\u015fme anahtar\u0131n\u0131n GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zda nas\u0131l pratik bir de\u011fer yaratabilece\u011fini g\u00f6stermektedir. Kod tekrar\u0131n\u0131 azaltarak, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n bak\u0131m\u0131n\u0131 kolayla\u015ft\u0131r\u0131r, hatalar\u0131 minimize eder ve genel olarak geli\u015ftirme s\u00fcrecinizi daha verimli hale getirir. Bu teknikleri kullanarak, CI\/CD s\u00fcre\u00e7lerinizi daha tutarl\u0131 ve \u00f6l\u00e7eklenebilir bir yap\u0131ya kavu\u015fturabilirsiniz. \u015eimdi, bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131 kullan\u0131rken dikkat etmeniz gereken baz\u0131 ileri d\u00fczey ipu\u00e7lar\u0131na ve p\u00fcf noktalar\u0131na g\u00f6z atal\u0131m.<\/p>\n<h2>\u0130leri D\u00fczey Kullan\u0131m \u0130pu\u00e7lar\u0131 ve P\u00fcf Noktalar\u0131<\/h2>\n<p>YAML \u00e7apalar\u0131, takma adlar ve birle\u015fme anahtar\u0131, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 daha d\u00fczenli hale getirmek i\u00e7in g\u00fc\u00e7l\u00fc ara\u00e7lard\u0131r. Ancak, bu ara\u00e7lar\u0131 etkili bir \u015fekilde kullanmak i\u00e7in baz\u0131 ileri d\u00fczey ipu\u00e7lar\u0131n\u0131 ve potansiyel tuzaklar\u0131 bilmek \u00f6nemlidir. \u0130\u015fte deneyimli kullan\u0131c\u0131lar\u0131n i\u015f ak\u0131\u015flar\u0131n\u0131 daha da optimize etmelerine yard\u0131mc\u0131 olacak baz\u0131 stratejiler:<\/p>\n<h3>1. Birle\u015fme Anahtar\u0131n\u0131n S\u0131ras\u0131 \u00d6nemlidir<\/h3>\n<p>Daha \u00f6nce de belirtti\u011fimiz gibi, birle\u015fme anahtar\u0131 <code>&lt;&lt;:<\/code> ile dahil edilen bir haritadaki anahtarlar, e\u011fer mevcut haritada ayn\u0131 anahtarlar varsa, mevcut haritadaki anahtarlar taraf\u0131ndan ge\u00e7ersiz k\u0131l\u0131n\u0131r. Bu, &#8220;son giren kazan\u0131r&#8221; kural\u0131d\u0131r. Bu kural, varsay\u0131lan de\u011ferleri tan\u0131mlay\u0131p daha sonra bunlar\u0131 \u00f6zelle\u015ftirmek i\u00e7in kritik \u00f6neme sahiptir. Bir haritada <code>&lt;&lt;: *alias<\/code> ifadesini nerede kulland\u0131\u011f\u0131n\u0131z, nihai \u00e7\u0131kt\u0131y\u0131 do\u011frudan etkiler.<\/p>\n<div class=\"code-container\">\n<pre><code>\ndefault_settings: &amp;defaults\n  timeout-minutes: 10\n  env:\n    DEBUG_MODE: \"false\"\n\njobs:\n  my_job:\n    &lt;&lt;: *defaults # Varsay\u0131lanlar \u00f6nce gelir\n    timeout-minutes: 5 # Varsay\u0131lan\u0131 ge\u00e7ersiz k\u0131lar\n    env:\n      DEBUG_MODE: \"true\" # Varsay\u0131lan\u0131 ge\u00e7ersiz k\u0131lar\n      APP_ENV: \"staging\" # Yeni bir anahtar ekler\n    steps:\n      - run: echo \"Job settings: timeout-minutes=5, DEBUG_MODE=true, APP_ENV=staging\"\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu \u00f6rnekte, <code>my_job<\/code>&#8216;un <code>timeout-minutes<\/code> de\u011feri <code>5<\/code> olacak ve <code>env<\/code> blo\u011fundaki <code>DEBUG_MODE<\/code> de\u011feri <code>true<\/code> olacakt\u0131r, \u00e7\u00fcnk\u00fc bunlar birle\u015fme anahtar\u0131ndan sonra tan\u0131mlanm\u0131\u015ft\u0131r ve varsay\u0131lanlar\u0131 ge\u00e7ersiz k\u0131lm\u0131\u015ft\u0131r.<\/p>\n<h3>2. \u0130\u00e7 \u0130\u00e7e \u00c7apalar ve Takma Adlar<\/h3>\n<p>YAML, i\u00e7 i\u00e7e ge\u00e7mi\u015f (nested) \u00e7apalar\u0131 ve takma adlar\u0131 destekler, ancak bu durum okunabilirli\u011fi ciddi \u015fekilde etkileyebilir. Bir \u00e7apa, ba\u015fka bir \u00e7apa i\u00e7eren bir blo\u011fu i\u015faret edebilir veya bir takma ad\u0131n i\u015faret etti\u011fi blok, ba\u015fka bir takma ad i\u00e7erebilir. Bu, g\u00fc\u00e7l\u00fc bir esneklik sunsa da, karma\u015f\u0131kl\u0131\u011f\u0131 art\u0131rabilir ve hata ay\u0131klamay\u0131 zorla\u015ft\u0131rabilir. Genellikle, en iyi uygulama, \u00e7apalar\u0131 daha basit, atomik (atomic) bloklar i\u00e7in kullanmakt\u0131r ve a\u015f\u0131r\u0131 i\u00e7 i\u00e7e ge\u00e7mekten ka\u00e7\u0131nmakt\u0131r.<\/p>\n<div class=\"code-container\">\n<pre><code>\n# \u0130\u00c7 \u0130\u00c7E \u00c7APALAR - Genellikle ka\u00e7\u0131n\u0131lmas\u0131 \u00f6nerilir\ncommon_env_vars: &amp;env_vars\n  APP_NAME: MyAwesomeApp\n  VERSION: 1.0.0\n\ncommon_steps: &amp;base_steps\n  - name: Ortak Ba\u015flang\u0131\u00e7\n    run: echo \"Starting ${{ *env_vars.APP_NAME }}\"\n    env: *env_vars # Ortam de\u011fi\u015fkenlerini dahil et\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      &lt;&lt;: *base_steps\n      - name: Build Uygulama\n        run: echo \"Building version ${{ *env_vars.VERSION }}\"\n      <\/code><\/pre>\n<\/p><\/div>\n<p>Bu \u00f6rnekte, <code>base_steps<\/code> \u00e7apas\u0131, <code>env_vars<\/code> \u00e7apas\u0131yla tan\u0131mlanan ortam de\u011fi\u015fkenlerini kullan\u0131r. Bu t\u00fcr bir yap\u0131, e\u011fer dikkatli kullan\u0131lmazsa, YAML dosyas\u0131n\u0131 \u00e7\u00f6z\u00fcmlenmesi zor bir hale getirebilir.<\/p>\n<h3>3. Okunabilirlik ve Karma\u015f\u0131kl\u0131k Dengesi<\/h3>\n<p>\u00c7apalar ve takma adlar, kod tekrar\u0131n\u0131 azaltmak i\u00e7in harika olsa da, a\u015f\u0131r\u0131 kullan\u0131m okunabilili\u011fi olumsuz etkileyebilir. \u00c7ok fazla \u00e7apa veya \u00e7ok karma\u015f\u0131k i\u00e7 i\u00e7e yap\u0131lar, i\u015f ak\u0131\u015f\u0131n\u0131 anlamay\u0131 zorla\u015ft\u0131rabilir. Bazen, k\u00fc\u00e7\u00fck bir tekrar, a\u015f\u0131r\u0131 soyutlamadan daha anla\u015f\u0131l\u0131r olabilir. Amac\u0131n\u0131z her zaman en k\u0131sa kodu yazmak de\u011fil, en s\u00fcrd\u00fcr\u00fclebilir ve anla\u015f\u0131l\u0131r kodu yazmak olmal\u0131d\u0131r. Ne zaman bir \u00e7apa kullanaca\u011f\u0131n\u0131za karar verirken, kendinize \u015fu soruyu sorun: &#8220;Bu soyutlama, i\u015f ak\u0131\u015f\u0131n\u0131 daha m\u0131 kolay yoksa daha m\u0131 zor anla\u015f\u0131l\u0131r hale getiriyor?&#8221;<\/p>\n<h3>4. YAML Ayr\u0131\u015ft\u0131r\u0131c\u0131 Farkl\u0131l\u0131klar\u0131 ve GitHub Actions<\/h3>\n<p>YAML&#8217;in farkl\u0131 s\u00fcr\u00fcmleri ve ayr\u0131\u015ft\u0131r\u0131c\u0131lar\u0131 (parser) aras\u0131nda k\u00fc\u00e7\u00fck farkl\u0131l\u0131klar olabilir. GitHub Actions, belirli bir YAML ayr\u0131\u015ft\u0131r\u0131c\u0131s\u0131 kullan\u0131r ve bu ayr\u0131\u015ft\u0131r\u0131c\u0131, \u00e7apalar\u0131, takma adlar\u0131 ve birle\u015fme anahtar\u0131n\u0131 belirli bir \u015fekilde yorumlar. Genellikle, bu \u00f6zellikler beklendi\u011fi gibi \u00e7al\u0131\u015f\u0131r, ancak nadir durumlarda uyumluluk sorunlar\u0131 ya\u015fanabilir. GitHub Actions belgelerini takip etmek ve karma\u015f\u0131k yap\u0131lar olu\u015fturmadan \u00f6nce k\u00fc\u00e7\u00fck testler yapmak, olas\u0131 sorunlar\u0131 \u00f6nlemeye yard\u0131mc\u0131 olabilir.<\/p>\n<h3>5. \u00c7apalar\u0131n Kapsam\u0131 (Scope)<\/h3>\n<p>Unutulmamal\u0131d\u0131r ki, YAML \u00e7apalar\u0131 sadece tan\u0131mland\u0131klar\u0131 dosya i\u00e7inde ge\u00e7erlidir. Farkl\u0131 YAML dosyalar\u0131 (yani farkl\u0131 GitHub Actions i\u015f ak\u0131\u015flar\u0131) aras\u0131nda \u00e7apalar\u0131 do\u011frudan payla\u015famazs\u0131n\u0131z. E\u011fer birden fazla i\u015f ak\u0131\u015f\u0131 dosyas\u0131nda ayn\u0131 yap\u0131land\u0131rmay\u0131 yeniden kullanman\u0131z gerekiyorsa, bu yap\u0131land\u0131rmay\u0131 ayr\u0131 bir dosya olarak tutmak ve onu her i\u015f ak\u0131\u015f\u0131nda ayr\u0131 ayr\u0131 tan\u0131mlamak veya GitHub Actions&#8217;\u0131n yeniden kullan\u0131labilir i\u015f ak\u0131\u015flar\u0131 (reusable workflows) \u00f6zelli\u011fini kullanmak daha uygun olabilir. Yeniden kullan\u0131labilir i\u015f ak\u0131\u015flar\u0131, t\u00fcm bir i\u015f ak\u0131\u015f\u0131n\u0131 veya bir i\u015fi ba\u015fka bir i\u015f ak\u0131\u015f\u0131nda \u00e7a\u011f\u0131rman\u0131za olanak tan\u0131r ve bu, \u00e7apalar\u0131n dosya i\u00e7i s\u0131n\u0131rlamalar\u0131n\u0131 a\u015fman\u0131n daha g\u00fc\u00e7l\u00fc bir yoludur.<\/p>\n<p>Bu ipu\u00e7lar\u0131 ve p\u00fcf noktalar\u0131, GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 \u00e7apalar, takma adlar ve birle\u015fme anahtar\u0131 ile daha etkili bir \u015fekilde y\u00f6netmenize yard\u0131mc\u0131 olacakt\u0131r. Bu ara\u00e7lar\u0131 bilin\u00e7li ve dengeli bir \u015fekilde kullanarak, CI\/CD s\u00fcre\u00e7lerinizi daha sa\u011flam, esnek ve bak\u0131m\u0131 kolay hale getirebilirsiniz. Her zaman oldu\u011fu gibi, en iyi pratikleri \u00f6\u011frenmek ve bunlar\u0131 kendi projelerinize uyarlamak, ba\u015far\u0131l\u0131 otomasyonun anahtar\u0131d\u0131r.<\/p>\n<h2>S\u0131k\u00e7a Yap\u0131lan Hatalar ve Ka\u00e7\u0131n\u0131lmas\u0131 Gereken Durumlar<\/h2>\n<p>YAML \u00e7apalar\u0131, takma adlar ve birle\u015fme anahtar\u0131, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde optimize edebilirken, yanl\u0131\u015f kullan\u0131ld\u0131\u011f\u0131nda beklenmedik sorunlara yol a\u00e7abilir. Bu b\u00f6l\u00fcmde, s\u0131k\u00e7a yap\u0131lan hatalar\u0131 ve bunlardan nas\u0131l ka\u00e7\u0131nabilece\u011finizi inceleyece\u011fiz.<\/p>\n<h3>1. Mevcut Olmayan \u00c7apalar\u0131 Referans G\u00f6stermek<\/h3>\n<p>En yayg\u0131n hatalardan biri, tan\u0131mlanmam\u0131\u015f bir \u00e7apay\u0131 takma ad ile referans g\u00f6stermektir. YAML ayr\u0131\u015ft\u0131r\u0131c\u0131s\u0131, b\u00f6yle bir durumda genellikle bir hata f\u0131rlat\u0131r ve i\u015f ak\u0131\u015f\u0131n\u0131z ba\u015far\u0131s\u0131z olur. Bu, genellikle yaz\u0131m hatalar\u0131ndan veya \u00e7apan\u0131n yanl\u0131\u015fl\u0131kla silinmesinden kaynaklan\u0131r.<\/p>\n<div class=\"code-container\">\n<pre><code>\n# HATA: 'yanlis_capanin_adi' diye bir \u00e7apa tan\u0131ml\u0131 de\u011fil\njobs:\n  my_job:\n    steps:\n      - &lt;&lt;: *yanlis_capanin_adi\n      <\/code><\/pre>\n<\/p><\/div>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong> \u00c7apalar\u0131 ve takma adlar\u0131 tan\u0131mlarken ve kullan\u0131rken dikkatli olun. B\u00fcy\u00fck i\u015f ak\u0131\u015flar\u0131nda, \u00e7apalar\u0131n tan\u0131mland\u0131\u011f\u0131 b\u00f6l\u00fcm\u00fc kolayca bulunabilir bir yere koymak ve tutarl\u0131 isimlendirme kurallar\u0131 kullanmak bu t\u00fcr hatalar\u0131 azalt\u0131r.<\/p>\n<h3>2. Yanl\u0131\u015f Girinti (Indentation) Kullan\u0131m\u0131<\/h3>\n<p>YAML, girintiye (bo\u015fluklara) duyarl\u0131 bir dildir. Yanl\u0131\u015f girinti, ayr\u0131\u015ft\u0131rma hatalar\u0131na veya beklenmeyen davran\u0131\u015flara yol a\u00e7abilir. \u00d6zellikle \u00e7apalar ve takma adlar kullan\u0131rken, bir blo\u011fun hangi seviyede ba\u015flad\u0131\u011f\u0131 ve bitti\u011fi \u00e7ok \u00f6nemlidir. Yanl\u0131\u015f girinti, bir \u00e7apan\u0131n kapsam\u0131n\u0131 yanl\u0131\u015f belirleyebilir veya bir takma ad\u0131n dahil edildi\u011fi yerin ba\u011flam\u0131n\u0131 bozabilir.<\/p>\n<div class=\"code-container\">\n<pre><code>\n# HATA: Yanl\u0131\u015f girinti nedeniyle YAML hatas\u0131\nmy_anchor: &amp;my_data\n  key1: value1\n    key2: value2 # Yanl\u0131\u015f girinti\n\njobs:\n  my_job:\n    steps:\n      - &lt;&lt;: *my_data\n      <\/code><\/pre>\n<\/p><\/div>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong> YAML dosyalar\u0131n\u0131z\u0131 d\u00fczenlerken tutarl\u0131 bir girinti stili (genellikle 2 bo\u015fluk) kullan\u0131n ve bir YAML linter (\u00e7\u00f6z\u00fcmleyici) veya IDE (Entegre Geli\u015ftirme Ortam\u0131) eklentisi kullanarak girinti hatalar\u0131n\u0131 otomatik olarak tespit edin.<\/p>\n<h3>3. Birle\u015fme Anahtar\u0131n\u0131 Yanl\u0131\u015f T\u00fcrlerle Kullanmaya \u00c7al\u0131\u015fmak<\/h3>\n<p>Birle\u015fme anahtar\u0131 <code>&lt;&lt;:<\/code>, yaln\u0131zca haritalar\u0131 (mappings\/objects) birle\u015ftirmek i\u00e7in tasarlanm\u0131\u015ft\u0131r. Bir listeyi (sequence\/array) veya skaler bir de\u011feri bir haritaya birle\u015ftirmeye \u00e7al\u0131\u015fmak bir hataya yol a\u00e7acakt\u0131r. \u00d6rne\u011fin, bir ad\u0131m listesini do\u011frudan bir haritaya dahil edemezsiniz, ancak bir harita i\u00e7indeki bir ad\u0131m listesini ba\u015fka bir harita i\u00e7indeki ad\u0131m listesine birle\u015ftirebilirsiniz.<\/p>\n<div class=\"code-container\">\n<pre><code>\n# HATA: Birle\u015fme anahtar\u0131 ile bir listeyi birle\u015ftirmeye \u00e7al\u0131\u015fmak (do\u011frudan)\nmy_list: &amp;steps_list\n  - name: Ad\u0131m 1\n    run: echo \"Ad\u0131m 1\"\n\njobs:\n  my_job:\n    steps:\n      &lt;&lt;: *steps_list # HATA: steps bir liste beklerken, buraya bir liste birle\u015ftirilemez\n      <\/code><\/pre>\n<\/p><\/div>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong> Birle\u015fme anahtar\u0131n\u0131 kullan\u0131rken, birle\u015ftirmeye \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131z veri t\u00fcrlerinin harita oldu\u011fundan emin olun. E\u011fer bir listeyi yeniden kullanmak istiyorsan\u0131z, bunu bir haritan\u0131n bir par\u00e7as\u0131 olarak tan\u0131mlay\u0131n veya listeleri do\u011frudan takma adlarla referans g\u00f6sterin.<\/p>\n<h3>4. A\u015f\u0131r\u0131 Optimizasyon ve Okunabilirlik Kayb\u0131<\/h3>\n<p>Kod tekrar\u0131n\u0131 azaltma arzusu, bazen a\u015f\u0131r\u0131 optimizasyona yol a\u00e7abilir. \u00c7ok fazla \u00e7apa, i\u00e7 i\u00e7e ge\u00e7mi\u015f takma adlar veya karma\u015f\u0131k ge\u00e7ersiz k\u0131lma mant\u0131\u011f\u0131 kullanmak, YAML dosyas\u0131n\u0131 o kadar karma\u015f\u0131k hale getirebilir ki, ilk ba\u015fta ama\u00e7lanan okunabilirlik ve bak\u0131m kolayl\u0131\u011f\u0131 tamamen kaybolur. Yeni bir geli\u015ftiricinin i\u015f ak\u0131\u015f\u0131n\u0131 anlamas\u0131 saatler s\u00fcrebilir.<\/p>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong> Her zaman okunabilirlik ve s\u00fcrd\u00fcr\u00fclebilirlik aras\u0131nda bir denge kurmaya \u00e7al\u0131\u015f\u0131n. E\u011fer bir soyutlama, i\u015f ak\u0131\u015f\u0131n\u0131 daha anla\u015f\u0131l\u0131r hale getirmiyorsa, belki de o soyutlamaya gerek yoktur. Basit tekrar, bazen karma\u015f\u0131k bir soyutlamadan daha iyidir. \u0130\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 d\u00fczenli olarak g\u00f6zden ge\u00e7irin ve gereksiz karma\u015f\u0131kl\u0131klardan ka\u00e7\u0131n\u0131n.<\/p>\n<h3>5. \u00c7apalar\u0131n Dosya Kapsam\u0131n\u0131 Yanl\u0131\u015f Anlamak<\/h3>\n<p>Yukar\u0131da da de\u011finildi\u011fi gibi, YAML \u00e7apalar\u0131 yereldir; yani yaln\u0131zca tan\u0131mland\u0131klar\u0131 YAML dosyas\u0131 i\u00e7inde ge\u00e7erlidir. Farkl\u0131 i\u015f ak\u0131\u015f\u0131 dosyalar\u0131 aras\u0131nda \u00e7apalar\u0131 do\u011frudan payla\u015famazs\u0131n\u0131z. Bu k\u0131s\u0131tlamay\u0131 g\u00f6z ard\u0131 etmek, i\u015f ak\u0131\u015flar\u0131n\u0131zda hata ararken kafa kar\u0131\u015f\u0131kl\u0131\u011f\u0131na yol a\u00e7abilir.<\/p>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong> Farkl\u0131 i\u015f ak\u0131\u015flar\u0131 aras\u0131nda ortak yap\u0131land\u0131rmalar\u0131 payla\u015fmak i\u00e7in GitHub Actions&#8217;\u0131n yeniden kullan\u0131labilir i\u015f ak\u0131\u015flar\u0131 (reusable workflows) \u00f6zelli\u011fini veya \u015fablon dosyalar\u0131n\u0131 kullan\u0131n. Bu yakla\u015f\u0131mlar, \u00e7apalar\u0131n dosya i\u00e7i s\u0131n\u0131rlamalar\u0131n\u0131 a\u015farak daha geni\u015f \u00e7apl\u0131 mod\u00fclerlik sa\u011flar.<\/p>\n<p>Bu hatalardan ka\u00e7\u0131narak, GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zda \u00e7apalar\u0131, takma adlar\u0131 ve birle\u015fme anahtar\u0131n\u0131 daha g\u00fcvenli ve etkili bir \u015fekilde kullanabilirsiniz. Unutmay\u0131n, bu ara\u00e7lar sorunlar\u0131 \u00e7\u00f6zmek i\u00e7in vard\u0131r, yenilerini yaratmak i\u00e7in de\u011fil. Do\u011fru kullan\u0131ld\u0131\u011f\u0131nda, CI\/CD s\u00fcre\u00e7lerinizi \u00f6nemli \u00f6l\u00e7\u00fcde geli\u015ftireceklerdir.<\/p>\n<h2>Sonu\u00e7 ve Gelecek Perspektifi<\/h2>\n<p>Bu makale boyunca, GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 daha verimli, s\u00fcrd\u00fcr\u00fclebilir ve y\u00f6netilebilir hale getirmek i\u00e7in YAML \u00e7apalar\u0131n\u0131n (anchors), takma adlar\u0131n (aliases) ve birle\u015fme anahtar\u0131n\u0131n (merge key) nas\u0131l kullan\u0131labilece\u011fini detayl\u0131 bir \u015fekilde inceledik. G\u00f6rd\u00fck ki, bu g\u00fc\u00e7l\u00fc YAML \u00f6zellikleri, tekrar eden kod bloklar\u0131n\u0131 ortadan kald\u0131rarak i\u015f ak\u0131\u015f\u0131 dosyalar\u0131n\u0131z\u0131 sadele\u015ftirmenin ve bak\u0131m maliyetlerini d\u00fc\u015f\u00fcrmenin anahtar\u0131n\u0131 sunuyor.<\/p>\n<p>Ba\u015flang\u0131\u00e7ta, GitHub Actions ve YAML&#8217;in temellerine de\u011finerek, tekrar eden kodun modern CI\/CD s\u00fcre\u00e7lerinde yaratt\u0131\u011f\u0131 sorunlar\u0131 ele ald\u0131k. Daha sonra, \u00e7apalar\u0131n bir veri blo\u011funu nas\u0131l i\u015faretledi\u011fini ve takma adlar\u0131n bu i\u015faretli blo\u011fu nas\u0131l referans g\u00f6sterdi\u011fini ad\u0131m ad\u0131m \u00f6rneklerle a\u00e7\u0131klad\u0131k. Birle\u015fme anahtar\u0131n\u0131n (<code>&lt;&lt;:<\/code>) ise haritalar\u0131 birle\u015ftirme ve \u00e7ak\u0131\u015fan anahtarlar\u0131 ge\u00e7ersiz k\u0131lma yetene\u011fiyle nas\u0131l esneklik sa\u011flad\u0131\u011f\u0131n\u0131 derinlemesine inceledik. Ger\u00e7ek d\u00fcnya senaryolar\u0131 arac\u0131l\u0131\u011f\u0131yla, matris i\u015flerinde ortak kurulum ad\u0131mlar\u0131n\u0131 veya farkl\u0131 ortamlar i\u00e7in da\u011f\u0131t\u0131m ad\u0131mlar\u0131n\u0131 optimize etme gibi pratik uygulamalar\u0131 g\u00f6sterdik.<\/p>\n<p>\u0130leri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131 ve s\u0131k\u00e7a yap\u0131lan hatalar b\u00f6l\u00fcmlerinde, bu ara\u00e7lar\u0131 kullan\u0131rken dikkat edilmesi gereken \u00f6nemli noktalar\u0131 vurgulad\u0131k. \u00d6zellikle birle\u015fme anahtar\u0131n\u0131n s\u0131ras\u0131n\u0131n \u00f6nemi, i\u00e7 i\u00e7e \u00e7apalar\u0131n potansiyel karma\u015f\u0131kl\u0131\u011f\u0131, okunabilirlik ile karma\u015f\u0131kl\u0131k aras\u0131ndaki denge ve \u00e7apalar\u0131n dosya kapsam\u0131 gibi konulara de\u011findik. Bu bilgiler, sadece kod tekrar\u0131n\u0131 azaltmakla kalmay\u0131p, ayn\u0131 zamanda i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n genel kalitesini ve anla\u015f\u0131l\u0131rl\u0131\u011f\u0131n\u0131 da art\u0131rman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<p>GitHub Actions s\u00fcrekli geli\u015fen bir platformdur ve otomasyon yetenekleri her ge\u00e7en g\u00fcn artmaktad\u0131r. YAML \u00e7apalar\u0131, takma adlar ve birle\u015fme anahtar\u0131 gibi \u00f6zellikler, bu evrimin temel yap\u0131 ta\u015flar\u0131ndan biridir. Bu teknikleri ustaca kullanarak, daha karma\u015f\u0131k ve \u00f6l\u00e7eklenebilir CI\/CD boru hatlar\u0131 olu\u015fturabilir, yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi daha da h\u0131zland\u0131rabilirsiniz. Unutmay\u0131n, iyi yap\u0131land\u0131r\u0131lm\u0131\u015f bir i\u015f ak\u0131\u015f\u0131, sadece hata oran\u0131n\u0131 azaltmakla kalmaz, ayn\u0131 zamanda ekiplerin daha verimli \u00e7al\u0131\u015fmas\u0131na ve yeniliklere odaklanmas\u0131na olanak tan\u0131r.<\/p>\n<p>\u015eimdi s\u0131ra sizde! Kendi GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 g\u00f6zden ge\u00e7irin. Tekrar eden bloklar\u0131, ortak yap\u0131land\u0131rmalar\u0131 veya benzer ad\u0131mlar\u0131 belirleyin. Ard\u0131ndan, bu makalede \u00f6\u011frendi\u011finiz \u00e7apalar\u0131, takma adlar\u0131 ve birle\u015fme anahtar\u0131n\u0131 kullanarak i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 optimize etmeye ba\u015flay\u0131n. Bu, CI\/CD yolculu\u011funuzda ataca\u011f\u0131n\u0131z \u00f6nemli bir ad\u0131m olacakt\u0131r.<\/p>\n<h3>S\u0131k\u00e7a Sorulan Sorular<\/h3>\n<h4>Soru 1: GitHub Actions&#8217;ta \u00e7apalar ve takma adlar ne i\u015fe yarar?<\/h4>\n<p><strong>Cevap:<\/strong> GitHub Actions&#8217;ta \u00e7apalar (<code>&amp;<\/code>) ve takma adlar (<code>*<\/code>), YAML dosyalar\u0131ndaki tekrar eden kod bloklar\u0131n\u0131 tan\u0131mlay\u0131p yeniden kullanmaya yarar. Bir \u00e7apa ile bir veri blo\u011funu i\u015faretler, takma ad ile de bu blo\u011fu i\u015f ak\u0131\u015f\u0131n\u0131z\u0131n farkl\u0131 yerlerinde referans g\u00f6stererek kod tekrar\u0131n\u0131 (DRY prensibi) azalt\u0131rs\u0131n\u0131z. Bu, i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131n daha s\u00fcrd\u00fcr\u00fclebilir, okunabilir ve y\u00f6netilebilir olmas\u0131n\u0131 sa\u011flar.<\/p>\n<h4>Soru 2: Birle\u015fme anahtar\u0131 (<code>&lt;&lt;:<\/code>) standart bir YAML \u00f6zelli\u011fi midir?<\/h4>\n<p><strong>Cevap:<\/strong> Hay\u0131r, birle\u015fme anahtar\u0131 (merge key) <code>&lt;&lt;:<\/code> standart bir YAML spesifikasyonu \u00f6zelli\u011fi de\u011fildir. Ancak, bir\u00e7ok YAML i\u015flemcisinde ve \u00f6zellikle GitHub Actions&#8217;ta yayg\u0131n olarak desteklenen bir uzant\u0131d\u0131r. Bu anahtar, bir haritan\u0131n i\u00e7eri\u011fini ba\u015fka bir haritaya dahil etmek i\u00e7in kullan\u0131l\u0131r ve \u00e7ak\u0131\u015fan anahtarlarda sonradan tan\u0131mlanan de\u011ferlerin ge\u00e7erli olmas\u0131n\u0131 sa\u011flar.<\/p>\n<h4>Soru 3: Farkl\u0131 dosyalardaki i\u015f ak\u0131\u015flar\u0131 aras\u0131nda \u00e7apalar\u0131 payla\u015fabilir miyim?<\/h4>\n<p><strong>Cevap:<\/strong> Hay\u0131r, YAML \u00e7apalar\u0131 yereldir ve yaln\u0131zca tan\u0131mland\u0131klar\u0131 YAML dosyas\u0131 i\u00e7inde ge\u00e7erlidir. Farkl\u0131 GitHub Actions i\u015f ak\u0131\u015f\u0131 dosyalar\u0131 aras\u0131nda \u00e7apalar\u0131 do\u011frudan payla\u015famazs\u0131n\u0131z. Farkl\u0131 i\u015f ak\u0131\u015flar\u0131 aras\u0131nda ortak yap\u0131land\u0131rmalar\u0131 veya ad\u0131mlar\u0131 payla\u015fmak i\u00e7in GitHub Actions&#8217;\u0131n &#8220;yeniden kullan\u0131labilir i\u015f ak\u0131\u015flar\u0131&#8221; (reusable workflows) \u00f6zelli\u011fini kullanman\u0131z \u00f6nerilir.<\/p>\n<h4>Soru 4: \u00c7apalar ve takma adlar performans\u0131 etkiler mi?<\/h4>\n<p><strong>Cevap:<\/strong> Hay\u0131r, \u00e7apalar ve takma adlar GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131n \u00e7al\u0131\u015fma zaman\u0131 performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde etkilemez. Bunlar, YAML dosyas\u0131n\u0131n ayr\u0131\u015ft\u0131rma (parsing) a\u015famas\u0131nda \u00e7\u00f6z\u00fcmlenir ve nihai i\u015f ak\u0131\u015f\u0131 tan\u0131m\u0131 olu\u015fturulur. \u00c7al\u0131\u015fma zaman\u0131nda, bu \u00e7\u00f6z\u00fcmlenmi\u015f tam yap\u0131land\u0131rma kullan\u0131l\u0131r. Dolay\u0131s\u0131yla, performans endi\u015fesi duymadan bu \u00f6zellikleri kullanabilirsiniz.<\/p>\n<h4>Soru 5: Hangi durumlarda \u00e7apalar yerine do\u011frudan tekrar eden kodu tercih etmeliyim?<\/h4>\n<p><strong>Cevap:<\/strong> \u00c7apalar ve takma adlar g\u00fc\u00e7l\u00fc olsa da, her zaman en iyi \u00e7\u00f6z\u00fcm de\u011fildir. E\u011fer bir kod blo\u011fu sadece iki veya \u00fc\u00e7 yerde kullan\u0131l\u0131yorsa ve \u00e7ok k\u0131sa ise, do\u011frudan tekrar etmek okunabilirlik a\u00e7\u0131s\u0131ndan daha iyi olabilir. A\u015f\u0131r\u0131 karma\u015f\u0131k veya i\u00e7 i\u00e7e ge\u00e7mi\u015f \u00e7apa yap\u0131lar\u0131, YAML dosyas\u0131n\u0131 anlamay\u0131 zorla\u015ft\u0131rabilir. Okunabilirlik ve bak\u0131m kolayl\u0131\u011f\u0131 aras\u0131ndaki dengeyi g\u00f6zetmek \u00f6nemlidir; bazen basit tekrar, a\u015f\u0131r\u0131 soyutlamadan daha anla\u015f\u0131l\u0131rd\u0131r.<\/p>\n<p>#GitHubActions #YAML #CI\/CD #Otomasyon #Yaz\u0131l\u0131mGeli\u015ftirme<\/p>\n","protected":false},"excerpt":{"rendered":"GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zda tekrar eden YAML kodlar\u0131ndan s\u0131k\u0131ld\u0131n\u0131z m\u0131?","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1401],"tags":[],"class_list":{"0":"post-45702","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-git","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131\" \/>\n<meta property=\"og:description\" content=\"GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zda tekrar eden YAML kodlar\u0131ndan s\u0131k\u0131ld\u0131n\u0131z m\u0131?\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-15T06:07:54+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"30 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131\",\"datePublished\":\"2026-11-15T06:07:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\"},\"wordCount\":4979,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Git\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\",\"name\":\"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-11-15T06:07:54+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/","og_locale":"tr_TR","og_type":"article","og_title":"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131","og_description":"GitHub Actions i\u015f ak\u0131\u015flar\u0131n\u0131zda tekrar eden YAML kodlar\u0131ndan s\u0131k\u0131ld\u0131n\u0131z m\u0131?","og_url":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-11-15T06:07:54+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"30 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131","datePublished":"2026-11-15T06:07:54+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/"},"wordCount":4979,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Git"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/","url":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/","name":"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-11-15T06:07:54+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/github-actions-yaml-tekrari-bitiren-capalar-takma-adlar-ve-birlesme-anahtari\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"GitHub Actions YAML: Tekrar\u0131 Bitiren \u00c7apalar, Takma Adlar ve Birle\u015fme Anahtar\u0131"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/45702","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=45702"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/45702\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=45702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=45702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=45702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}