Sports Games Gitlab Io Work

This file tells GitLab how to build and deploy the game. For sports games (which are usually pure JavaScript/Canvas games), the file is remarkably simple:

pages:
  stage: deploy
  script:
    - mkdir .public
    - cp -r * .public
    - mv .public public
  artifacts:
    paths:
      - public
  only:
    - main

When this file exists, GitLab automatically runs the pipeline. Within minutes, your sports game is live on gitlab.io. sports games gitlab io work

The magic starts when a developer pushes code to their GitLab repository. This file tells GitLab how to build and deploy the game

This is the "Work" part of the keyword. The game doesn't run on a server; the deployment work happens via GitLab, and the runtime work happens in your browser. When this file exists, GitLab automatically runs the

| Component | Technology / Tool | |-----------|-------------------| | Frontend | HTML5, CSS3, Vanilla JavaScript (ES6) | | Game Rendering | Canvas API / SVG | | State Management | LocalStorage, SessionStorage | | Version Control | Git (GitLab) | | CI/CD | GitLab CI/CD (.gitlab-ci.yml) | | Hosting | GitLab Pages | | Testing | Jest (unit), Playwright (E2E) | | Analytics | Self-hosted Plausible (optional) |

To ensure your sports game works on GitLab.io, you need this:

pages:
  stage: deploy
  script:
    - mkdir .public
    - cp -r * .public
    - mv .public public
  artifacts:
    paths:
      - public
  only:
    - main

If you want to help improve existing projects: