Regulations files that are not in git about worldcubeassociation.org HOT 10 CLOSED

For now, I'd prefer wca-documents to stay purely dedicated to the text of the Regulations. (Each branch only has textual changes – or translations.)

I would suggest a new branch on cubing/wca-documents-extra , or a general data branch in this repo.

from worldcubeassociation.org.

A new branch on cubing/wca-documents-extra sounds nice to me (I'd rather not have wca-documents-extra know anything about this repo (worldcubeassociation.org), just seems cleaner to me to not have a dependency cycle). I'll investigate this today. Do you have any preference for branch name? Does a general data branch on wca-documents-extra sound good?

I just noticed https://github.com/blog/1986-announcing-git-large-file-storage-lfs today. Do you have any knowledge about it?

from worldcubeassociation.org.

A data branch sounds good. I'd go for a branch instead of something else fancy for now (even if it makes wca-documents-extra slow by default).

from worldcubeassociation.org.

Sounds great! Git clone doesn't bring down branches other than master by default, right?

from worldcubeassociation.org.

Sounds great! Git clone doesn't bring down branches other than master by default, right?

Uh, very false?
I haven't checked in a while, but I'm pretty sure it brings all branches.

from worldcubeassociation.org.

Yeah:

Clones a repository into a newly created directory, creates remote-tracking branches for each branch in the cloned repository

from worldcubeassociation.org.

Interesting. I have some fundamental gaps in my knowledge of how git works. I thought that all data is stored in the .git folder, but it's only 17MB in a fresh clone, when we have 50+ MB of stuff in our data branch...

~/tmp @kaladin> git clone [email protected]:cubing/wca-documents-extra.git w2
~/tmp @kaladin> cd w2
~/tmp/w2 @kaladin> git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
~/tmp/w2 @kaladin> git branch
* master
~/tmp/w2 @kaladin> du -h .
...
18M .
~/tmp/w2 @kaladin> git fetch origin data:data
From github.com:cubing/wca-documents-extra
 * [new branch]      data       -> data
~/tmp/w2 @kaladin> du . -h
...
18M .
~/tmp/w2 @kaladin> git branch
  data
* master
~/tmp/w2 @kaladin> du . -h
~/tmp/w2 @kaladin> git checkout data
Switched to branch 'data'
~/tmp/w2 @kaladin> du . -h
...
80M .
~/tmp/w2 @kaladin> git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
~/tmp/w2 @kaladin> du . -h
...
18M .

Anyways, looks like you're right.

from worldcubeassociation.org.

If we're willing to suffer the consequences of a (more) painful initial git clone, why not commit these files into wca-documents-extra directly, instead of in a new branch?

from worldcubeassociation.org.

Because that doesn't let us change our mind about where to put the files without amending history. ;-)

from worldcubeassociation.org.

Closing this as it has been dealt with =)

from worldcubeassociation.org.