-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: dont mark version as dirty temporarily and investigate git status #2008
Conversation
git diff | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this for logging @gak?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I need to see what is causing the repo to be dirty.
type ModuleSecret struct { | ||
ID int64 | ||
CreatedAt time.Time | ||
Module optional.Option[string] | ||
Name string | ||
Url string | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing this is unrelated, but needed to be checked in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is related to code generated in the CI causing the repo to be dirty. I'm under the impression these sqlc files needed to be checked in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your impression is correct :) Looks like whoever added ModuleSecret to the db schema just didn't know they needed to run just build-sqlc
.
No description provided.