<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CI/CD on Game Server Services | Docs</title>
    <link>/tags/ci/cd/</link>
    <description>Recent content in CI/CD on Game Server Services | Docs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/tags/ci/cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CI/CD for Master Data</title>
      <link>/articles/master_data/cicd/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/articles/master_data/cicd/</guid>
      <description>Automating master data updates can reduce human error and speed up the development cycle.&#xA;Automation Flow The general automation flow is as follows:&#xA;Data Creation: Create master data using Excel, Google Sheets, CSV, etc. Conversion: Convert from spreadsheets to GS2 master data format (JSON). Commit: Commit the converted JSON or GS2-Deploy template to a Git repository. Deployment: CI tools (GitHub Actions, CircleCI, etc.) detect changes and reflect them in GS2. Automating Deployment Using GS2-Deploy If you embed master data in a GS2-Deploy template, you can reflect changes by updating the GS2-Deploy stack from your CI.</description>
    </item>
  </channel>
</rss>
