-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
added new blog post, corresponding images, and a new config file #186
base: main
Are you sure you want to change the base?
Conversation
…ncludes/figure.liquid"
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.
No blocking comments. Just a few pointers that you might want to update. If not, give me a ping and I merge this PR. If you want to adjust the PR I will gladly re-review the article. Thanks for the contribution!
I will get the PR updated as you described. Should be ready by tomorrow. |
@sus-admin If you want I would merge this. Or do you want to patch up anything before we merge this PR? |
@SchoolGuy go ahead and merge, thanks. I will start working on some PRs for my other guides, I'm very interested in your feedback and how I can help get some more fixes included in a future release. |
@sus-admin First feedback is an oversight of mine during the review. I do desire that all commits are signed via GPG. Is that something you can do? |
@SchoolGuy I tried to retroactively sign these commits, but not sure if it's valid or not. please merge the PR, or cancel it and I will submit a new one with signed commits. |
@sus-admin The first commit is not yet signed. The best way forward for you is probably to squash all your commits since they touch one blog post. When doing so you automatically should create a new commit that is either signed by default or when you give the |
No description provided.