-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the ISKTER Wiki! This will contain any relevant information to help document any useful information related to this project.
If you'd like to add a resource to this growing list, please do the following:
-
Fork the repository.
-
Clone the repository from the one you forked.
git clone https://github.com/github_username/ISKTER.git
-
Change directories into the repository.
cd ./ISKTER
-
Create a new branch with your username here on GitHub and checkout the branch.
git checkout -b github_username
-
You'll need to also set your upstream for this new branch using the following command:
git branch -u origin/github_username
-
Add the resource link you'd like to share into the
README.md
file.If you have multiple resources being added or you're making a lot of changes in the file, , don't use
-m
to bring up your default editor used by git and document each change on a separate line starting with a-
. -
Once you've updated the
README.md
file with the appropriate resources, add the file to be committed.git add README.md
-
Commit the change.
git commit -m "Added the best text editor, vim."
-
Push your change back to your repository on GitHub.
git push
-
Create a pull request on GitHub.
- Be sure to indicate in the title what was done very briefly and then detail what you added and any additional changes you made. Be sure to set Allow edit by maintainers is checked in case I need to correct any small/minor typos or mistakes that could arise during the pull request or the pull request will be reject.
- Once I receive the request, I will review it as soon as I am able to. If you have any questions, feel free to reached out to me on my various social media accounts so I can help clarify anything I left ambiguous or you feel like you didn't understand.
Please follow these guidelines when formatting the resource being linked.
- [Title of Resource](https://url_of_resource): Very brief description explaining the resource being sure to note what others should be sure to look for.
Categories are marked with a Heading 2 using ##
and sub-categories using a Heading 3 ###
.
If the resource does not fall into the given sub-categories currently available, create a new one and place it into the appropriate category, making sure that it's placement is in alphabetic order to other sub-categories within that category. If neither sub-categories or categories available fit where the resource should be, create a new category. Be aware that I may move the categories around or shift them into sub-categories to better organize where they make sense.
Avoid linking to a given file directly and instead link to the resource's website or GitHub/GitLab project page.