Open cyber-sourceress opened 1 year ago
Can you go back and edit your history and force-push a new commit without these .DS_Store
s so they're not in the history please?
I'm not sure your intent with your new .md file vs your .html file, I see their content is entirely different - are you planning to move all of the content in the HTML into the .md file?
I'm not sure your intent with your new .md file vs your .html file, I see their content is entirely different - are you planning to move all of the content in the HTML into the .md file?
Yes, in the final the text of the html (not the html nor formatting, just the relevant text) goes into the md. I just wasn't ready to edit the .md at the time.
Yeah! I'll go do that.
On Mon, Mar 6, 2023 at 5:36 PM Vega Deftwing @.***> wrote:
Can you go back and edit your history and force-push a new commit without these .DS_Stores so they're not in the history please?
— Reply to this email directly, view it on GitHub https://github.com/VegaDeftwing/OpGuidesHugoSrc/pull/44#issuecomment-1457216172, or unsubscribe https://github.com/notifications/unsubscribe-auth/APADUGL64C72TPSHLK7GVMDW2ZYIXANCNFSM6AAAAAAVQYWT5U . You are receiving this because you authored the thread.Message ID: @.***>
@cyber-sourceress Sometime ™️ Eventually ™️ I'll probably clean this up and merge it unless you want to finish it up. Shoot me a message on Discord if you do still want to!
Aside from figuring wording for a few parts then an editing pass, I largely have it complete.
I was typing it up in html for speed but will be posting the actual article in md, I just wanted to make certain I had a competent grasp of md first.
Apologies for the delay, it's been crazy.
Thank you for submitting a pull request!
Before I (Vega) can merge your content I just need to deal with how to license and credit your contribution.
First things first,
Not checking this box does not mean I will deny your pull request outright, it just means we may need to have a look at how likely we are to be called out on using whatever content you've used.
Pick one of these 3 Options:
1) Public Domain
[ X] I agree to put my contribution into the Public Domain (or CC-0, if that doesn't apply where you are)
[ X] (not required) I would like to be credited as: Nicolette Grimm on the OpGuides Homepage
2) CC-NC-BY-SA 4.0 With Exceptions
[ ] I agree that my content will be licensed as CC-NC-BY-SA 4.0
[ ] I agree that acknowledgment of contribution on the homepage of OpGuides or any fork is sufficient for fulfilling the obligation in the license to provide credit to my contributions (your name doesn't need to appear on the same page as your contribution)
I would like to be credited as: ____ on the OpGuides Homepage
[ ] I agree that Vega can still collect donations though the site (an exception to the 'NC' terms of the license)
[ ] I agree that Vega or one other person - "The Backup" - Vega appoints at a time may grant this same exception to those wishing to host a fork of OpGudides themselves. In the event that Vega is unable to grant this exception further, the last person appointed "The Backup" becomes the copyright holder of the OpGuides name, logo, Interviews, and blog posts and may appoint a new "The Backup" for the same purpose.
3) Copyright Assignment
[ ] I agree to assign the copyright of this contribution to Vega
And Done!
If you have any questions about the license or have any concerns about your PR, please don't hesitate to ask!