From 7efd34cd17601e6e063429ffc69380058f74adf0 Mon Sep 17 00:00:00 2001
From: Jeff Carr <jcarr@wit.com>
Date: Thu, 9 Jan 2025 21:39:33 -0600
Subject: [PATCH] Notes added by 'git notes append'

---
 e242a7a41f83d68b899ad19722595292d9ffbd3d | 96 ++++++++++++++++++++++++
 1 file changed, 96 insertions(+)

diff --git a/e242a7a41f83d68b899ad19722595292d9ffbd3d b/e242a7a41f83d68b899ad19722595292d9ffbd3d
index 9c70fd1..03e03f3 100644
--- a/e242a7a41f83d68b899ad19722595292d9ffbd3d
+++ b/e242a7a41f83d68b899ad19722595292d9ffbd3d
@@ -1230,3 +1230,99 @@ func (all *GoDeps) selectAllGoDep() []*GoDep {
 }
 
 // `autogen:repo.marshal.pb.go`
+
+package gitpb
+
+// Code generated by go.wit.com/apps/autogenpb. DO NOT EDIT.
+// This file was autogenerated with autogenpb v0.0.37 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 *Repo) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *Repo) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *Repo) 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 *Repo) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *Repo) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *Repo) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *Repo) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}
+
+// human readable JSON
+func (v *Repos) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *Repos) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *Repos) 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 *Repos) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *Repos) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *Repos) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *Repos) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}