Test

fix: bug where when adding multiple objects across a yaml tree, we ended up re-using memory which could have downstream effect #27

	name: Test

	on:
	pull_request:
	branches:
	- main
	types:
	- opened
	- edited
	- synchronize
	- reopened

	jobs:
	build:
	name: Conventional pull request names
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
	- uses: amannn/action-semantic-pull-request@0723387faaf9b38adef4775cd42cfd5155ed6017 # v5.5.3
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	build-test:
	name: Build & Test
	if: ${{ github.event.pull_request.draft == false }}
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
	with:
	submodules: true
	- name: Set up Go
	uses: actions/setup-go@3041bf56c941b39c61721a86cd11f3bb1338122a # v5.2.0
	with:
	go-version-file: "go.mod"
	- name: Set up Node
	uses: actions/setup-node@39370e3970a6d050c480ffad4ff0ed4d3fdee5af # v4.1.0
	with:
	node-version: "18.x"
	registry-url: "https://registry.npmjs.org"
	- name: Set up gotestfmt
	run: go install github.com/gotesttools/gotestfmt/v2/cmd/gotestfmt@latest
	- name: Build
	run: go build ./...
	- run: go test -json -v -p 1 ./... \| gotestfmt

Provide feedback