A Very Simple Guide to Forking on GitHub | The Princess of The Night

diff --git a/accessibility/index.html b/accessibility/index.html index 2cfe246b..db35d4b7 100755 --- a/accessibility/index.html +++ b/accessibility/index.html @@ -394,11 +394,11 @@

Contents:

There are, of course, other ways to write dates so as to not confuse people. 10/Dec/1993 is quick to understand, for example.

-

Displaying text art

+

Displaying text art

-

Text art is notoriously cumbersome for those who use screen-readers. This is because, as text art is mostly based around symbols and letters organized in a way to create an image rather than, well, text.

+

Text art is notoriously cumbersome for those who use screen-readers. This is because, as text art is mostly based around symbols and letters organized in a way to create an image rather than, well, text.

-

When publishing text art online, people usually use the <pre> tag. By adding a simple <aria-hidden="true"> to a tag such as <pre> or <span> (example below), the content it contains will not be read by screen-readers (as described in WAI-ARIA 1.0).

+

When publishing text art online, people usually use the <pre> tag. All test in this element are displayed in a fixed-width font and the text will preserve both spaces and line breaks - it will show up the same way that it is written in the source code. By adding a simple <aria-hidden="true"> to a tag such as <pre> or <span> (example below), the content it contains will not be read by screen-readers (as described in WAI-ARIA 1.0).

      "AAARRrrrggghhh! Back Evil! You can't stop my quest
             for The Holly Ascii..IVANOHHHEEEEE"
@@ -422,6 +422,10 @@ Contents:
                           ,((,-,__\  '', __\_/. __,'
                                        ''./_._._-'

+

In the code, it will look something like this:

+ +

<pre aria-hidden="true">ASCII art goes here</pre>

+

Of course, it will be still necessary to describe the art if it relevant to the topic at hand. A possible solution to this issue is describing the «image» afterwards with regular text tags. If the text art is meant to be purely decorative, you can probably skip this step though.

Final thoughts

@@ -447,7 +451,7 @@

Contents:

document.write(year) by Cass «Owly» Python and Bruno «devils» A. of yourdevilfriends.art. Please see humans.html for full credit and thanks. Peace and love.

The song used for Transcripts and Subtitles is «Gonna Dig Up Alec Guinness» by Lemon Demon from the album «Damn Skippy» (2005). I, Cass, am doubtful that the use of this song would fall under fair use in the USA or fair dealing in the UK, but according to the ReadMe.txt from the official website, «feel free to use any of this music in any video/animation projects for school or for fun».

-

The ASCII art used on this page was made by Joris «b'ger» Bellenger from their website. A copyright notice page exists on the site that reads:

+

The ASCII art used on this page was made by Joris «b'ger» Bellenger from their website. A copyright notice page exists on the site that reads:

You may freely copy and distribute the ascii art found on this site provided that use of such ascii art is for non-commercial or personal use only. Use for any other purpose is expressly prohibited without the author's written permission.
diff --git a/end/index.html b/end/index.html index ab50ea73..2cf5b024 100644 --- a/end/index.html +++ b/end/index.html @@ -78,7 +78,7 @@

-
"The End"
by Julian Gough
+
"The End"
Julian Gough

I see the player you mean.
diff --git a/howto/git/001.png b/howto/git/001.png new file mode 100644 index 00000000..e85da7a6 Binary files /dev/null and b/howto/git/001.png differ diff --git a/howto/git/002.png b/howto/git/002.png new file mode 100644 index 00000000..aa949caf Binary files /dev/null and b/howto/git/002.png differ diff --git a/howto/git/003.png b/howto/git/003.png new file mode 100644 index 00000000..f6ba3760 Binary files /dev/null and b/howto/git/003.png differ diff --git a/howto/git/004.png b/howto/git/004.png new file mode 100644 index 00000000..d2ed1d19 Binary files /dev/null and b/howto/git/004.png differ diff --git a/howto/git/005.png b/howto/git/005.png new file mode 100644 index 00000000..8b44de03 Binary files /dev/null and b/howto/git/005.png differ diff --git a/howto/git/index.html b/howto/git/index.html new file mode 100644 index 00000000..1da804b8 --- /dev/null +++ b/howto/git/index.html @@ -0,0 +1,94 @@ + + + + + A Very Simple Guide to Forking on GitHub | The Princess of The Night + + + + + + + + + + + + + + + + + +
A Very Simple Guide to Forking on GitHub
+
+
+
If you are new to GitHub and you want to help with a project but don't know where to start, it might seem a little confusing what to do and where to begin, so this simple guide will show the basics of how to use forking on GitHub.
+ +
Before anything, you will need to have a GitHub account.
+ +
Step 1: Find the git you want to contribute to
+
On your browser, go to the git that you want to make changes to, in this case, we're on this git. In simple terms, a git is a place that holds all of the code, pictures, sound, and everything else that is used in that project.
+ +
If it is for a computer game, then it will have the assets for the game, if it is a website, then it will have stuff like HTML, CSS, etc on it. Git is unique as you can see the edit history for the project and who made that change and when.
+ +
+ +
Step 2: Go fork yourself!
+
On the git that you want to fork, move your mouse to Fork and then to Create a new fork. Once you do this, your browser will redirect you to a new webpage that will let you decide on what the name of your fork for the project should be. A lot of the time, it's fine to just keep this all the same, so just press Create fork.
+ +
And boom. You now have your own version of the project. You can make your own changes to this and the original won't be affected at all. Think of it like printing a picture off of the Internet and drawing on it - the original won't change at all.
+ +
+ +
Step 3: Making changes
+
Now that you have your own version of the git, you can make changes to it. On GitHub, you can simply just drag and drop your new files to the git. You can also delete files as well by clicking on the three dots icon that will be next to Add file button that you will see when you are either in a folder or when you are in a file.
+ +
Once you are happy with your changes, there will be a box that says Commit changes, here you can give a title to your changes and write a description of it. Once happy, click on the green button.
+ +
+ +
Step 4: Making a pull request (PR)
+ +
You can now make a pull request (PR). This will send a message to the git of the original project that anyone can see. In this message, people usually write down their changes, why they should be added, and anything else important.
+ +
Click on the Pull request button. This will lead you to a new page. Now, press on New pull request.
+ +
You will once again be redirected to a new page that will show all of the changes that you made to the project. When you send in a PR, other people will also be able to see the changes that you made to the project. Once happy, press the very nice Create pull request button.
+ +
+ +
Now is your time to shine. Write about all of the changes that you made and why they should be merged (added) to the project). Once you are happy with what you have done, click the Create pull request button for a final time.
+ + +
Step 5: Now you wait
+ +
Once you have sent out a new PR, the owner (and also anyone who follows the project) will get an E-Mail and a ping to say that you have sent out this request. On GitHub, there is a comment section on this page where people can talk about your pull.
+ +
If the owner likes it, they will merge it, effectively adding it to their project. If the owner does not agree with the changes, they can outright reject what you did. If they want something changed, you can fix up the code by changing it on the fork that you made. You will not have to send another pull request.
+ +
+ +
Hopefully, your changes do get added. Once they do, you will be able to see yourself be credited on the Contributors section of the original git.
+ +
Happy forking!
+ +
+
+
+ +
Want to support OwlyFans? See our NFTs!

The text is copyrighted 2021 - by Cass «Owly» Python, licensed under the FOPL-MDP. Please see humans.html for full credit and thanks. Peace and love.
★
+
+
+τ +
+
+
+ + + + \ No newline at end of file diff --git a/start/index.html b/start/index.html index e0f4fbc4..5b6c66b1 100644 --- a/start/index.html +++ b/start/index.html @@ -83,7 +83,7 @@

-
«The Start»
by Cass Python
+
«The Start»
Cass Python

Did you see that? Look, it's them. Look down and see.