I am tring to resopnd to your responce in order an put number by them so they can be referred back to later if needed without copy and past…
- Thanks for taking the time to respond
Your welcome and thank for responding. I am hard to deal with an realy appreciate you taking the time.
The top portion of my post was just to explain that I have tried to search for my anwer l(like the other document on posting i read told me to do) and explain why my tone is not the best.
about my issuse in finding the info i want
It is still ongoing but not realy related to this post. It deals with tring to find out the reason for fork and maybe even discuse, forking in general. I feel that you should tell the reason for the fork and git hub should encourage you to tell the reason. It dose not look like github does this and requieres me to do a lot more posting to explain why i think it is a very important feature to have if it does it it dose not explain how to use it.
my issue with the course is still going on becuase i have not completed it yet but i going to mark it as solved because what you said should work for any problem i have and you also told me Github labs does use webhooks
4)I don’t think i am still stuck. Even though I don’t think reseting it is the best option and User friendly.
5)I can not send you a link that cuase the merge conflect becuase I reseted my course. However i beleave i can redublicate it. It told me in the issue to edit my readme file describtion and i edit the text in the readme file itself with the describtion there Instead of
the describtion of the file. I did not realise they where two differnt things opps.
- The last Issue about what I want to see change are these things
1.)Add text into the issue #1 readme that states something to the like of “Becareful not to edit the text of the describtion of readme it will cause a merge conflect when I go and creates a pull request latter in this course”
2.) Add text into the pull request that states :"Becareful when You Commiting your changes in this tutorial you have to do this twice and the green commit button is located in two differnt spots the
1st) Spot in the code reviewer wich approve the textual changes of the pull request and commits the pull request to the add-doc branch. And a
2nd) time to commit the add-doc branch to the master branch for more info about branching see this video and (give link back to the one you created for you github tutorial) and or take our other course(give link to gethub-lab-tutorial)
3)If you don’t see the green commit button after doing the 1st scroll down more on this pull request to see the button.
- add Please also note: There also a differnce between a merge where your work with someone else and a comment where you just approve of the changes of someone else work without much modification.
I feel this should prevent people from doing what i done. I called it a bug becuase your do’t want to hang the robbot".
I also want to add" In this course will be pretending you be working with mono in the team of devlopers etc…"
I want to discuse this more but I probaly should put this else where i would also like to see each lab link to a form post to talk about the problem and improvment need for that course.
****to sum up above more than what you should have to do *****
Please also note on the other spot on getlab community where it ask if you want to work on our course drop us a note I said i want to work on this course but did not go though this much details.
Thanks again for read and helping me on this difficault journey and i apollogize for getting a little of topic.