[dwgdev]

Wow.. that indeed was a very very good advices. Thank you so much for your time to give a very detailed list in the areas that I must improve.

1) I did not understand about "most code on the initial commit". I have been updating the code basically every day. Is it because I have a dummy account? Like the accomplishment I wrote in the README, I recently put the dates I accomplish them.

2) About the repos, I think it has a lot because I recently cancelled the subscription. And I can't put them back to private. I will consider paying for the subscription and add back to private.

3) CalendarData is a repo where I can modify it with my app called: "MyAgenda" which is private since it contains a key to make HTTP requests via Basic Authorization.

I will definitely rework my GitHub page. :)

[rickyc091]

Ahh, sorry, an initial commit is the first commit you do on a repository. In this case, I noticed that most of the code logic was on this commit (https://github.com/woguan/Legend-Wings/commit/0df03c7657cc13...). It's actually better to have multiple commits to show your progress and thought process.

Well, the nice thing about git is that you can just remove the repo from GitHub and then push it back later. I would definitely recommend removing things like tutorials. I personally would rather see your school work than tutorials. Referring to (https://github.com/woguan/FlappySwift/commits/master)

For CalendarData, it might be better to add a README and add some context to it. Better yet, it's probably better to just hide it altogether since I interpreted the repo as you learning how to use JSON 6 months ago. If you need to store the JSON somewhere, one suggestion is to use gists https://gist.github.com/.

To publish private code that requires a private key, look into ENV variables.

These links might be able to help you if you don't know about ENVs already.

https://stackoverflow.com/questions/7501678/set-environment-... https://stackoverflow.com/questions/36219597/referring-to-en...