[Tutorial] How to get help #65
Mara-Li
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sometimes, it is difficult to debug and understand why the plugin doesn't work. So, to help you, I created this "to-do" list, to make a proper calling for help. Please read it before post something in Q&A!
Before posting
Github Publisher
only. Some error are common :Common limitation of the plugin
Before posting to get help, here some limitation I can't do anything :
My repository is exploded
If you fail, you can revert the merging branch using GitHub : Here is a tutorial
If you can't revert, or if the revert doesn't work, you need to manually do it. First, check the PR number that explode your repo. You can get it using the Pull Requests menu, or checking the folder that have been edited by this PR.
After, you need to create a branch :
[Publisher] Merging #{PR number - 1}
for example,#625
if it's the#626
PR.View commit details
:4. Click on the browse file button
5. Click on the commit number and type the branch name, for example, revert :
6. Now, you need to open : A local terminal console (if you have git installed) or a codespace (if you have any) for this repository. Don't forget to
git pull
if you have already cloned the repository.7. You need to be on your main branch, so first :
git checkout main
; After, you have to rungit checkout revert <path to edited file or folder>
. If you want to take an entire folder, for exampledocs
, just typedocs/.
. It will take all file8.
git commit -am "restoring folder" && git push
. If you use VScode, you can also use the menu to ordering your file restoration.How to get help
So, if you can't found any solution to your problem, here is a form you have to fill when posting :
It is possible you get a real bug, so the discussion can be turned into an issue!
Beta Was this translation helpful? Give feedback.
All reactions