If it's solid work, you're proud of it, and you don't mind sharing it with the world, then sure! Having examples of past code to point at is always helpful, especially when you're very early in your career and have little else to distinguish yourself with. It's even better if you think that someone else might find use in the thing.
That is... assuming that it's a personal project, or otherwise somehow unique to you. If the "big project" you're referring to is effectively homework for a class, and everyone else in class is also producing a PDP8 Computer simulation in C, then it's a lot less interesting.
Additionally, it's probably a good idea to keep adding projects to your account as you go. Being able to show progression to your potential employers when you go for your interview is great. Having the only example of your code be the thing that you bodged together as a freshman is not so great.
...and for the next project, you could even start out with the thing on github, and use it as the source control tool it's meant to be. There's a number of kids out there your age who don't really understand about source control, and having a low-key way of indicating that you're not one of those, without making a thing about it is all upside and no downside.