Skip to content

ci: Setup GitHub Actions, project documentation, and codebase formatting#6

Closed
NAME-ASHWANIYADAV wants to merge 5 commits into
agones-dev:mainfrom
NAME-ASHWANIYADAV:ci/format-and-github-actions
Closed

ci: Setup GitHub Actions, project documentation, and codebase formatting#6
NAME-ASHWANIYADAV wants to merge 5 commits into
agones-dev:mainfrom
NAME-ASHWANIYADAV:ci/format-and-github-actions

Conversation

@NAME-ASHWANIYADAV

Copy link
Copy Markdown
Contributor

Type of change

  • 🐛 Bug fix
  • 🚀 New feature / enhancement
  • 📖 Documentation
  • 🧹 Refactoring / cleanup
  • ⚙️ CI / tooling
  • ⚠️ Breaking change

What this PR does

This PR establishes the foundation for project health, CI/CD, and open-source contributions.

Specifically, it introduces:

  1. GitHub Actions CI Pipeline: Automatically builds, type-checks, lints, formats, and tests the code on every push/PR. Includes concurrency control to cancel stale runs and artifact uploads for easy reviewer testing.
  2. Project Documentation: Adds a comprehensive CONTRIBUTING.md with guidelines for branching and conventional commits, a SECURITY.md policy, and an updated README.md.
  3. Issue/PR Templates: Standardised templates for Bug Reports, Feature Requests, Documentation gaps, and Pull Requests to guide new contributors.
  4. Codebase Formatting: Ran npm run format (Prettier) across the entire codebase to enforce consistent styling. Updated .gitignore to properly track the .github directory.
  5. Unit Testing: Added production-grade unit tests using Vitest for the StateChip component and buildAllocationBody utility to ensure reliability of GameServer state mapping and allocation payload generation.
  6. Dependabot: Added configuration for automated npm and github-actions dependency updates.

Related issues

Supersedes and closes #3 (Enhance project documentation and CI setup)

Screenshots / recordings

N/A - No user-facing UI changes, only CI/CD and tooling.

Test plan

Automated checks

  • npm ci
  • npm run build
  • npm run tsc
  • npm run lint
  • npm run format -- --check
  • npm run test (28 tests passing)

Manual verification

  • Verified that .github files are tracked properly.
  • Tested the plugin build locally without errors.

RBAC considerations

No RBAC changes required.

Notes for reviewers

This PR includes the groundwork started in #3 but expands upon it with codebase formatting, Vitest unit tests, and CI concurrency control.

Update .gitignore to add an exception for the .github folder. This is
required so that the GitHub Actions CI workflows and templates can be
committed and tracked by Git, as they were previously excluded by the
global '.*' rule.

Signed-off-by: ashwani yadav <22ashwaniyadav@gmail.com>
Enhance the repository documentation to support open source contributions.
This includes adding a comprehensive CONTRIBUTING.md, a SECURITY.md
policy, issue templates for bugs and features, a pull request template,
and updating the README to link to these new resources.

Signed-off-by: ashwani yadav <22ashwaniyadav@gmail.com>
Introduce a CI pipeline to automatically build, lint, format, and test
the plugin on every pull request and push to the main branch. Includes
concurrency control, pinned actions, artifact uploads, and Dependabot
configuration to keep dependencies updated.

Signed-off-by: ashwani yadav <22ashwaniyadav@gmail.com>
Introduce robust unit tests for the StateChip component and the
buildAllocationBody utility using Vitest. This ensures that GameServer
lifecycle state colors map correctly and allocation payload generation
handles all form edge cases properly.

Signed-off-by: ashwani yadav <22ashwaniyadav@gmail.com>
Run 'npm run format' across the entire codebase to enforce consistent
code styling. This resolves all Prettier formatting violations and ensures
the code complies with the project's formatting standards for CI.

Signed-off-by: ashwani yadav <22ashwaniyadav@gmail.com>
@NAME-ASHWANIYADAV NAME-ASHWANIYADAV force-pushed the ci/format-and-github-actions branch 2 times, most recently from 7d9f078 to 9585ddd Compare June 10, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant