Re: [oll-user] [Challenges] Important: cleaning up
Resources for LilyPond and LaTeX users writing (about) music
Status: Alpha
Brought to you by:
u-li-1973
From: Joshua N. <jos...@gm...> - 2014-01-13 22:54:00
|
I'm sorry that I haven't done it yet; being in CST and without my computer, I'm sure you are thinking "What is taking so long!?" I'll be on it very soon. IC, Josh On Mon, Jan 13, 2014 at 4:50 PM, Janek Warchoł < lem...@gm...> wrote: > (please reply asap!) > > Hi all, > > I think my previous email about repository cleanup&maintenance may have > not reached everyone, since some people who forked the repo seem not to be > on the mailing list. Since i want to avoid creating confusion during > cleanup, i'd like to ask every participant to look at my previous email > (quoted below), perform the steps listed there and notify me that i can > proceed. > > I apologize for the inconvenience. > > best, > Janek > > > 2014/1/13 Janek Warchoł <lem...@gm...> > >> it turned out that our setup was not perfect (a bit too complicated) - it >> would be nice to do some clean up to make sure that any confusion is >> reduced to minimum (especially for any new participants that may appear). >> >> Of course, we have everything under control, so don't worry! :-) >> >> Here are instructions for cleanup: >> >> 1) stop working on challenges until the cleanup is finished (hopefully >> everything should be ready again tomorrow). >> >> 2) make sure that all your work is committed. Use 'git status' for that: >> if there are any "modified" files, or any "untracked" files that are part >> of your work and should be submitted (e.g. engraving files of your program, >> such as .sib or .musx files) you should add them using 'git add filename' >> and do a 'git commit'. >> >> 3) make sure that all your work is pushed ("uploaded") to your github >> fork: >> first, make sure that 'git status' says "working directory clean". Check >> if you have remote repository configured properly ('git remote -v' should >> list a remote named 'origin' pointing to your github fork). Use 'git >> branch' to see all your local branches (some of you will probably have just >> one - master. That'll make things easier :) ). Then, for each branch do >> the following: >> git checkout branchname >> git push origin branchname >> >> And check if you can see your work using GitHub's website. >> >> I apologize for inconvenience. >> > -------------- next part -------------- An HTML attachment was scrubbed... |