From e5ae1141cd5ad32a2fdc9f87be50dcdc4e91c0f6 Mon Sep 17 00:00:00 2001
From: Jeff Carr <jcarr@wit.com>
Date: Mon, 16 Dec 2024 00:36:08 -0600
Subject: [PATCH] Notes added by 'git notes append'

---
 3673578031572d461a5ef2b2a8b3ab51adb3e6c7 | 95 ++++++++++++++++++++++++
 1 file changed, 95 insertions(+)

diff --git a/3673578031572d461a5ef2b2a8b3ab51adb3e6c7 b/3673578031572d461a5ef2b2a8b3ab51adb3e6c7
index f83697f..7b895e9 100644
--- a/3673578031572d461a5ef2b2a8b3ab51adb3e6c7
+++ b/3673578031572d461a5ef2b2a8b3ab51adb3e6c7
@@ -631,3 +631,98 @@ func (all *GitTags) selectAllGitTag() []*GitTag {
 }
 
 // `autogen:goDep.marshal.pb.go`
+
+package gitpb
+
+// This file was autogenerated with autogenpb v0.0.28 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 *GoDep) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *GoDep) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *GoDep) 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 *GoDep) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *GoDep) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *GoDep) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *GoDep) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}
+
+// human readable JSON
+func (v *GoDeps) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *GoDeps) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *GoDeps) 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 *GoDeps) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *GoDeps) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *GoDeps) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *GoDeps) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}