-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is this needed? #1
Comments
I want to make it easy for newer members that don't know git as well to find and look at the old code. Most newer member have no clue how to make commits much less look at old tagged ones, so if they want to look at old code as a reference of sorts of how theirs should be structured this is much easier to find. |
@greg-bahr It's possible to link to an individual commit or tag in GitHub. I think as a compromise there should be a wiki page somewhere (LoA?) that keeps lists of every tag link so people can click on them and see what it looked like. EDIT: |
Mitchell,
Not everything needs to be done the "proper" way on GitHub. Making the code easy to access and read through for new members is more important than proper use of git tagging and etc. Creating a new repo is an easy way for new members to look back at code without having to learn the intricacies of git.
… On Jul 6, 2017, at 7:16 PM, Mitchell Skaggs ***@***.***> wrote:
@greg-bahr It's possible to link to an individual commit or tag in GitHub. I think as a compromise there should be a wiki page somewhere (LoA?) that keeps lists of every tag link so people can click on them and see what it looked like.
Here's an example: 2015-2016 Season.
That uses the full commit ID, but if a tag was created, you could link to that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Here's a step-by-step tutorial:
Now your tag will be present in the GitHub "Releases" tab under the "Tags" button. You can copy the link to send to anyone and they will be able to view the code as it was then. It's much more complicated to have yet another repository to maintain along with each individual one. |
The new repo would only need to be updated once a year or so. Its easy for a senior member to simply update a new repo once a year then teach new members how to use git in a command terminal. I would even be comfortable sifting through old tagged commits in the terminal, much less a new member.
Joshua Zahner
[email protected]
314-378-2989
joshuazahner.com
… On Jul 6, 2017, at 8:30 PM, Mitchell Skaggs ***@***.***> wrote:
Here's a step-by-step tutorial:
Find the name of the commit by clicking backwards in the repo. It's going to be really long.
Run the command `git tag "20XX-20XX-Season-Final" "COMMIT_NAME"
Run the command git push origin --tags
If step 3 fails, run git pull and go back to step 3
Now your tag will be present in the GitHub "Releases" tab under the "Tags" button. You can copy the link to send to anyone and they will be able to view the code as it was then. It's much more complicated to have yet another repository to maintain along with each individual one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIs5kHXx6Iy7eKbSxMGVgf1gQqDOEvOLks5sLYoxgaJpZM4OQGzH>.
|
That footer is disgusting. :) |
Josh what the hell is that footer :-) |
Its my default one for talking to potential website clients. Why is this the concern?
Joshua Zahner
[email protected]
314-378-2989
joshuazahner.com
… On Jul 6, 2017, at 9:47 PM, Yasaman (Yasi) Mostafavi ***@***.***> wrote:
Josh what the hell is that footer :-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIs5kF3HJ4Z_cYK3pOPIViH0v9DTffWQks5sLZw-gaJpZM4OQGzH>.
|
Back to the topic, I feel that portraying GitHub as a file-storage system by copying and organizing versions using folders is disingenuous to whole purpose of Git. What advantage does this repository serve over merely linking to a shared Google Drive folder? I wager that new programmers would find Google Drive even easier than GitHub! This solution doesn't help teach new programmers why Git is much more than a complicated Google Drive. EDIT: This website seems extremely helpful for teaching simple Git concepts before ramping up into branches and merging http://learngitbranching.js.org/ |
@greg-bahr This can be replaced by instead tagging commits in each team's repository. Git is designed to store the entire history of the code.
The text was updated successfully, but these errors were encountered: