From c12a6f3d69d1c99e1ea7bb8f44bd9e17b2c74e5c Mon Sep 17 00:00:00 2001
From: Jeff Carr <jcarr@wit.com>
Date: Wed, 8 Jan 2025 04:17:19 -0600
Subject: [PATCH] Notes added by 'git notes append'

---
 0ca1240c7556829d0a43b58a5ea608b6b71e79aa | 95 ++++++++++++++++++++++++
 1 file changed, 95 insertions(+)

diff --git a/0ca1240c7556829d0a43b58a5ea608b6b71e79aa b/0ca1240c7556829d0a43b58a5ea608b6b71e79aa
index 02fae55..16640ad 100644
--- a/0ca1240c7556829d0a43b58a5ea608b6b71e79aa
+++ b/0ca1240c7556829d0a43b58a5ea608b6b71e79aa
@@ -34,3 +34,98 @@ google.golang.org/protobuf v1.36.2 h1:R8FeyR1/eLmkutZOM5CWghmo5itiG9z0ktFlTVLuTm
 google.golang.org/protobuf v1.36.2/go.mod h1:9fA7Ob0pmnwhb644+1+CVWFRbNajQ6iRojtC/QF5bRE=
 
 // `autogen:gitTag.marshal.pb.go`
+
+package gitpb
+
+// This file was autogenerated with autogenpb v0.0.36 DO NOT EDIT
+//     go install go.wit.com/apps/autogenpb@latest
+//
+// You can use it on simple protobuf files
+// The .proto file must have a singular and plural form of a message
+// (for those of you that know ruby on rails, it's like that)
+//
+// You can mark which repos you want to auto generate sort.pb.go and marshal.pb.go files for
+//
+// For an example,
+//       go-clone go.wit.com/lib/protobuf/gitpb
+//
+
+import (
+	"google.golang.org/protobuf/encoding/protojson"
+	"google.golang.org/protobuf/encoding/prototext"
+	"google.golang.org/protobuf/proto"
+)
+
+// human readable JSON
+func (v *GitTag) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *GitTag) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *GitTag) UnmarshalJSON(data []byte) error {
+	return protojson.Unmarshal(data, v)
+}
+
+// apparently this isn't stable, but it's awesomely better
+// https://protobuf.dev/reference/go/faq/#unstable-text
+// it's so great for config files, I'm using it by default to try to fix the problems with it
+func (v *GitTag) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *GitTag) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *GitTag) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *GitTag) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}
+
+// human readable JSON
+func (v *GitTags) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *GitTags) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *GitTags) UnmarshalJSON(data []byte) error {
+	return protojson.Unmarshal(data, v)
+}
+
+// apparently this isn't stable, but it's awesomely better
+// https://protobuf.dev/reference/go/faq/#unstable-text
+// it's so great for config files, I'm using it by default to try to fix the problems with it
+func (v *GitTags) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *GitTags) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *GitTags) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *GitTags) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}