What's new

Tutorial Simple guide to using GitHub

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

L&LD

Part of the Furniture
@JGrana, I agree.

Is there a 10-step program/tutorial for GitHub navigation/comprehension? :)
 
@JGrana, I agree.

Is there a 10-step program/tutorial for GitHub navigation/comprehension? :)
In three simple steps :)

Part one, the Overview
Navigate to my repository on GitHub: https://github.com/decoderman
k46acnnbg7z.png



Part two, the files
pyvdcaadgyk.png



Part three, getting an idea what changes were made
6yxkcbbgw7w.png
 
Something I have been better at doing is using the Releases properly: https://github.com/jackyaz/connmon/releases
This serves as a single point to see all changes made for a particular script/project without maintaining a separate changelog file.
And Github users can “Watch” the repository to be notified of new Releases when published. But notification only works if there is text in the Release, I believe.
 
Last edited:
In three simple steps :)

Part one, the Overview
Navigate to my repository on GitHub: https://github.com/decoderman
k46acnnbg7z.png



Part two, the files
pyvdcaadgyk.png



Part three, getting an idea what changes were made
6yxkcbbgw7w.png


Something I have been better at doing is using the Releases properly: https://github.com/jackyaz/connmon/releases
This serves as a single point to see all changes made for a particular script/project without maintaining a separate changelog file.


Holy cow...........you guys are unbelievable,such a painkillers for me,thanks for both handy men.
 
I gratefully appreciate all the contributions here! Everything helps.

@thelonelycoder's 3 step guide is a big start, but the 'what' or, more accurately the 'why' of what has changed or been fixed is still a black hole to me. I know I would need to learn to code to understand the nuances. I don't want to just be able to discern an extra space or a missed period (for example), I want to know how it affects the script from the perspective of the user.

@Jack Yaz's 'Releases' is much more user-friendly and more suited to the 'GitHub for Dummies' series types of books I can more readily relate to. :)

Of course, with the @thelonelycoder's method, I will eventually 'understand' more and more 'coding'. I would love to travel to that land and be able to order some cheese and wine by myself! :D

Keep up the splendid work gentlemen! Ignore the ramblings of an old member who once thought nothing could be harder than BASIC.
 
I gratefully appreciate all the contributions here! Everything helps

Keep up the splendid work gentlemen! Ignore the ramblings of an old member who once thought nothing could be harder than BASIC.

Let me guess - second hardest was COBOL. ;-)
 
I thought I was the only one who had difficulty gittin' around on github.

I appreciate all the help there already, but it would be good to have a bare bones tutorial for those greenhorns (like me) and explain things like, for instance, what is a Pull Request? I've decided that a Push is when the final version is released.

But don't spend any time on it. I don't see how you guys have any time at all with what all you do on the side as it is.

thanks again,
jts
 
There are many articles on this. Just search "git primer" or "github primer". If all you want is to grab a distro, you can just download a zip using the link found when clicking the Code button.
 
@thiggins thanks for that suggestion.

However, most if not all of those are focused on programmers, not on users of the code...
 
What do "users of the code" need besides how to download a distro?
 
They need to know what changes between versions.

They need to know what the changes that are made, affect them, and their usage.

They need to know if any assumptions of the script of the previous build has changed in the new code.
 
Those things are not a function of Git. They are up to the developer to document in release notes.
 
That is why we need a thread here at snbforums.com that doesn't expire in 6 months. :)
 
That is why we need a thread here at snbforums.com that doesn't expire in 6 months. :)

A 6 month expiration does not prevent such a thread from existing. What you need rather is a developer willing to provide such a thread. I see lots of us here who seem to be doing just fine doing that for our respective projects.
 
Actually RMerlin, it does.

Instead of one thread where we can check as we can, we now have to search for a needle in a haystack in multiple threads with very similar titles.

Unless the correct thread happens to be extremely active, it quickly falls to the wayside.
 
Instead of one thread where we can check as we can, we now have to search for a needle in a haystack in multiple threads with very similar titles.

Unless the correct thread happens to be extremely active, it quickly falls to the wayside.

Set filter to desired addon. Find first post in the list coming from addon author. There, you're done.

If you find that more complicated than figuring out how to navigate around Github, then you must be missing something about how to use a public forum.

Bottom line is, nobody is preventing him from providing support threads here. He made a conscious choice not to do so. His call.
 
The new rule tax is not so much on the users as it is on the developers as they now have to watch multiple threads to provide support for their addons. Adam was replying to support questions and feature requests for Skynet almost every day which is one of the reasons the thread grew so big.

Doing that on a list of several threads is like having to go through a (messy) ticketing system queue on your spare and unpaid time. Some developers are prepared to do so (at least for now), others aren't and that's understandable. Adam decided to leave on the first day but others may follow later or reduce their contributions if they get tired or bored by too much admin work which most techies tend to loathe.

Since third party developers are an important factor of the success of the forum and the firmware I don't think it was a good idea to risk chasing them away for a rule that brings in a much smaller comparative value.

For the users the bigger problem is that now Adam is no longer around to provide support and possibly development for his addon.
 
The new rule tax is not so much on the users as it is on the developers as they now have to watch multiple threads to provide support for their addons. Adam was replying to support questions and feature requests for Skynet almost every day which is one of the reasons the thread grew so big.

Doing that on a list of several threads is like having to go through a (messy) ticketing system queue on your spare and unpaid time. Some developers are prepared to do so (at least for now), others aren't and that's understandable. Adam decided to leave on the first day but others may follow later or reduce their contributions if they get tired or bored by too much admin work which most techies tend to loathe.

Since third party developers are an important factor of the success of the forum and the firmware I don't think it was a good idea to risk chasing them away for a rule that brings in a much smaller comparative value.

For the users the bigger problem is that now Adam is no longer around to provide support and possibly development for his addon.
It doesn't bother me. I do helpdesk support as my day job so this change doesn't faze me at all. You're all stuck with me!
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top