imported>PvME corpus import: Attributed pinned PvME snapshot 074a9438f79d10fba75735791be0030734db8b5e; CC BY-NC-SA 4.0

2026-11-11T14:25:57Z

Attributed pinned PvME snapshot 074a9438f79d10fba75735791be0030734db8b5e; CC BY-NC-SA 4.0

New page

[[PvME|PvME guide index]]

<h2 id="introduction"><ins><nowiki>Introduction</nowiki></ins></h2>
<nowiki>
</nowiki><nowiki>This guide will go over an assortment of common issues you may encounter while working with GitHub, as well as a few helpful things you can do to streamline your workflow.</nowiki>
<nowiki>
</nowiki><nowiki>Note: You can always ask any editor or staff for help with GitHub at any time.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><h2 id="frequently-used-terminology"><ins><nowiki>Frequently Used Terminology</nowiki></ins></h2>
<nowiki>
</nowiki><nowiki>⬥ </nowiki><nowiki>Repository</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• A collection of all the files and folders for a single project, that is tracked and version controlled.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ </nowiki><nowiki>Fork</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• A </nowiki><nowiki>copy</nowiki><nowiki> of an entire repository. A user can </nowiki><nowiki>fork</nowiki><nowiki> a repository to get a personal copy.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ </nowiki><nowiki>Commit</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• Essentially a 'snapshot' of your repository. Think of it like a checkpoint in a video game. Going back to a particular commit shows the entire repository as it was at that point in time. You commit after making your changes, to prepare for a pull request.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ </nowiki><nowiki>Pull Request</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• A request to merge </nowiki><nowiki>your changes</nowiki><nowiki> into the </nowiki><nowiki>main repository</nowiki><nowiki>, to be accepted by someone with appropriate permissions.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><h2 id="common-problems"><ins><nowiki>Common Problems</nowiki></ins></h2>
<nowiki>
</nowiki><h3 id="failed-checks"><nowiki>Failed Checks</nowiki></h3>
<nowiki>
</nowiki><nowiki>⬥ PvME GitHub is set up to automatically check for valid formatting and styling. There are a number of checks, such as:</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• Trailing whitespace - extra space at the end of a line</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• Improper spacing around emojis - emojis must be surrounded by a space on either side</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• Message length exceeded (too many characters) - messages cannot exceed 2000 characters</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• Invalid embed formatting - creates an invalid embed object.</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• Invalid commands - any </nowiki><code><nowiki>.command:</nowiki></code><nowiki> ‎used must be a valid command.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Checks failing can be avoided by using the </nowiki><nowiki>web editor</nowiki><nowiki> (</nowiki>[https://pvme.github.io/guide-editor/ <nowiki>https://pvme.github.io/guide-editor/</nowiki>]<nowiki>) to edit your content before adding it to GitHub, as it runs the same style checks that pull requests use. For more information check out, </nowiki>[[PvME/Contributing/Guide Editor|<nowiki>Guide Editor</nowiki>]]<nowiki>.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ If your pull request fails due to a check, it will inform you. Click on </nowiki><nowiki>Details</nowiki><nowiki> on the check to see why it has failed, and what you can do to fix it.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Consider the following example:</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/ZxizF57.png <nowiki>Guide illustration</nowiki>]
<nowiki>
</nowiki>[https://img.pvme.io/images/qdZjUvf.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ The bottom red square tells you what the error is. In this case, the message starting at line 108 and ending at line 139 has too many characters.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ To fix this, click the </nowiki><nowiki>Edit File</nowiki><nowiki> option in the following image, to open up editing again to make appropriate changes.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/WHpF7Wq.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ In this case, we break the single large message into 2 separate messages by hitting </nowiki><code><nowiki>Enter</nowiki></code><nowiki>, entering a single period </nowiki><code><nowiki>.</nowiki></code><nowiki> ‎and hitting </nowiki><code><nowiki>Enter</nowiki></code><nowiki> ‎again. Then commit these changes, and it will update the pull request.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/fTIpYv5.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Your Pull Request should now be error-free once the checks complete again.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><h3 id="checks-are-stuck"><nowiki>Checks Are Stuck</nowiki></h3>
<nowiki>
</nowiki><nowiki>⬥ Rarely, the style and syntax checks may get stuck, neither succeeding nor failing. In such an event, usually merging a different minor pull request tends to resolve the issue.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Checks can take some time to complete at times, so wait for at least 20-30 minutes before it is considered an issue.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ In case this occurs, you can contact an editor or staff for assistance.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><h3 id="your-branch-is-x-commits-behind-master"><nowiki>Your Branch Is 'X' Commits Behind Master</nowiki></h3>
<nowiki>
</nowiki><nowiki>⬥ When you make a new fork, your fork will look like this:</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/j3kEy55.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ However, after some time it may look something like this:</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/ztJQ0wj.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ This is because changes might have happened to the main repository (</nowiki><code><nowiki>'X' commits behind</nowiki></code><nowiki>) and it is no longer in-sync with your copy. This may cause issues when making a pull request.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ To resolved this, </nowiki><nowiki>the simplest solution is to delete your fork, and make a new fork of the PvME repository</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ This will give you a fresh, up-to-date copy, and get rid of any lingering issues.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><nowiki>For more experienced users</nowiki><nowiki>: PvME squashes and merges all pull requests. This causes a difference in commit hashes, which is why your branch will be both ahead AND behind in commits after a pull request is accepted. You can clean this up by discarding commits from accepted PRs and syncing your branch to pvme:master. Or by resetting your branch to pvme:master. Or just delete and start over.|</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><h2 id="pull-requests"><ins><nowiki>Pull Requests</nowiki></ins></h2>
<nowiki>
</nowiki><h3 id="multiple-changes-updating-an-existing-pull-request"><nowiki>Multiple Changes & Updating an Existing Pull Request</nowiki></h3>
<nowiki>
</nowiki><nowiki>⬥ It is possible to include changes to multiple files within the same Pull Request, and to amend files you have already modified as part of that Pull Request.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ This can be helpful to reduce the number of PRs being opened, and remove the need of closing a PR and reopening it if a mistake has been made.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><nowiki>Note: It is assumed you have already forked the repository.</nowiki>
<nowiki>
</nowiki><nowiki></nowiki>
<nowiki>
</nowiki><nowiki>⬥ Consider the scenario: a pull request has been made, with changes to </nowiki><nowiki>one</nowiki><nowiki> file, visible in the </nowiki><nowiki>Files Changed</nowiki><nowiki> tab.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/kxvu0O2.png <nowiki>Guide illustration</nowiki>]<nowiki>
</nowiki>
<nowiki>
</nowiki><h3 id="modify-an-existing-file-in-the-pull-request"><nowiki>Modify an Existing File in the Pull Request</nowiki></h3>
<nowiki>
</nowiki><nowiki>To make an a change to a file that already contains a change, </nowiki><nowiki>in the same pull request</nowiki><nowiki>, do the following.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Navigate to your Pull Request, and go to the </nowiki><nowiki>Files Changed</nowiki><nowiki> tab.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Go to the top right corner of the file you wish to update, click the three dots, then </nowiki><nowiki>Edit File</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/h2i3Rkb.jpg <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Make whatever additional changes you like, and then </nowiki><nowiki>Commit directly to the xxx branch</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/GbkYLNi.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Navigate back to your Pull Request, and the additional change should be included!</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/OxtPQXE.png <nowiki>Guide illustration</nowiki>]<nowiki>
</nowiki>
<nowiki>
</nowiki><h3 id="add-a-new-file-to-the-pull-request"><nowiki>Add a New File to the Pull Request</nowiki></h3>
<nowiki>
</nowiki><nowiki>To edit a different file, and include it in the same pull request, do as follows,</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Navigate to your Pull Request and click on the name of your branch, here:</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• You are now looking at the main directory of your own branch, where all files will reside.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/ylNa85w.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Locate the additional file you would like to change, open it, and then click the edit icon.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/kSt0Xpa.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Make whatever changes you like, and then </nowiki><nowiki>Commit directly to the xxx branch</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/sa6tPYh.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Navigate back to your Pull Request, and the additional file should be included!</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/UKnKrfs.png <nowiki>Guide illustration</nowiki>]<nowiki>
</nowiki>
<nowiki>
</nowiki><h2 id="helpful-tips"><ins><nowiki>Helpful Tips</nowiki></ins></h2>
<nowiki>
</nowiki><h3 id="file-split-view"><nowiki>File Split View</nowiki></h3>
<nowiki>
</nowiki><nowiki>⬥ When opening a Pull Request, it is good practice to look at your changes and see if any mistakes have been made.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ By default, you will see differences between your changes and the original file in </nowiki><nowiki>Unified View</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Sometimes, especially for larger changes, it can be helpful to use </nowiki><nowiki>Split View</nowiki><nowiki> instead.</nowiki>
<nowiki>
</nowiki><nowiki>⬥ Navigate to your Pull Request, and go to the </nowiki><nowiki>Files Changed</nowiki><nowiki> tab.</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• By default, you will see unified changes, as shown below:</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/KqtUExJ.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Click the settings icon, select </nowiki><nowiki>Split</nowiki><nowiki>, and then </nowiki><nowiki>Apply and reload</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/mqNCNlT.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Congratulations! From now on, your changes will be shown in </nowiki><nowiki>Split View</nowiki><nowiki>.</nowiki>
<nowiki>
</nowiki><nowiki>‎ ‎ ‎ ‎• You can reverse the process to go back to a unified view at any time, if you prefer.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/IAz8bya.png <nowiki>Guide illustration</nowiki>]<nowiki>
</nowiki>
<nowiki>
</nowiki><h3 id="bulk-replacing"><nowiki>Bulk Replacing</nowiki></h3>
<nowiki>
</nowiki><nowiki>⬥ To bulk replace, either navigate to the </nowiki><nowiki>Edit</nowiki><nowiki> menu then select </nowiki><nowiki>Replace in Files</nowiki><nowiki> or use the Ctrl+Shift+H keybind to do the same.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/avBqR0i.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ Doing this will open the </nowiki><nowiki>Search/Replace</nowiki><nowiki> side menu.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/bLoBXsg.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ The search box is where you enter what you want to replace and the replace box is where you enter what you want to replace it with.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/1aRteP5.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ However, most of these results aren't what we're looking for so can be dismissed by hovering over the number to the right and clicking the X to dismiss the whole file or the individual Xs below to dismiss individual matches.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/acVwcaR.png <nowiki>Guide illustration</nowiki>]<nowiki>
⬥ When you find something you want to replace. you can either right click and click Replace to do it one at a time or you can click the icon to the left of the X to replace all matches in a file.</nowiki>
<nowiki>
</nowiki>[https://img.pvme.io/images/wolcMdJ.png <nowiki>Guide illustration</nowiki>]<nowiki>
</nowiki>
<nowiki>

</nowiki>
== Attribution and source history ==
Adapted from [https://pvme.io/pvme-guides/editor-resources/github-tutorials/github-tips-and-troubleshooting/ <nowiki>Github Tips And Troubleshooting</nowiki>] by PvME contributors. [https://github.com/pvme/pvme-guides/commits/master/editor-resources/github-tutorials/github-tips-and-troubleshooting.txt Upstream source history]. Licensed [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA 4.0]. Snapshot 074a9438f79d10fba75735791be0030734db8b5e. Formatting adapted for standalone MediaWiki; media and third-party references remain external links.

PvME/Contributing/Github Tips And Troubleshooting - Revision history

imported>PvME corpus import: Attributed pinned PvME snapshot 074a9438f79d10fba75735791be0030734db8b5e; CC BY-NC-SA 4.0