Skip to content
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

Open
magneticflux- opened this issue Jul 6, 2017 · 9 comments
Open

Why is this needed? #1

magneticflux- opened this issue Jul 6, 2017 · 9 comments
Labels

Comments

@magneticflux-
Copy link
Member

@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.

@greg-bahr
Copy link
Contributor

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.

@magneticflux-
Copy link
Member Author

magneticflux- commented Jul 7, 2017

@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.

EDIT:
This is a link to the tag I just created: link

@Ovec8hkin
Copy link
Member

Ovec8hkin commented Jul 7, 2017 via email

@magneticflux-
Copy link
Member Author

magneticflux- commented Jul 7, 2017

Here's a step-by-step tutorial:

  1. Find the name of the commit by clicking backwards in the repo. It's going to be really long.
  2. Run the command git tag "20XX-20XX-Season-Final" "COMMIT_NAME"
  3. Run the command git push origin --tags
  4. 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.

@Ovec8hkin
Copy link
Member

Ovec8hkin commented Jul 7, 2017 via email

@skeltonn
Copy link
Member

skeltonn commented Jul 7, 2017

That footer is disgusting. :)

@YasiTL
Copy link

YasiTL commented Jul 7, 2017

Josh what the hell is that footer :-)

@Ovec8hkin
Copy link
Member

Ovec8hkin commented Jul 7, 2017 via email

@magneticflux-
Copy link
Member Author

magneticflux- commented Jul 7, 2017

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.
In addition, this is duplicating data that is already stored elsewhere. Git keeps a record of every version of every file ever added to a repository, so the information is already right at the user's fingertips. Is it so much to ask programmers to learn the command git checkout [thing you want to checkout]?

EDIT: This website seems extremely helpful for teaching simple Git concepts before ramping up into branches and merging http://learngitbranching.js.org/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants