A few parting words

Nobody has claimed this yet.

# Nice Work


Congratulations @Mesmoraz, you've completed this course! :tada:

## What went well

Before I say good-bye, I want to recap all the tasks you've accomplished. You:

- Learned what to do with an empty repo on GitHub :sparkles:
- Created a .gitignore and removed bulky binaries
- Used your favorite local tools to push existing code
- Set your code up in a GitHub repository :fireworks:

## What's Next?

Now that you've moved your Git repository to GitHub, managing your repository and adding collaborators are common next steps. Here are some recommended courses we think you might be interested in:

[Community Starter Kit](https://lab.github.com/courses/community-starter-kit)
Hosting a project on GitHub enables you to share your work with millions of other developers. This course will walk you through the different items you can add to your repository to welcome new contributors and make it easier for them to report issues, suggest new features, or potentially submit a pull request!

[Create a release based workflow](https://lab.github.com/courses/create-a-release-based-workflow)
Now that you have a repository on GitHub learn how to utilize a release workflow to create new releases for your project through an efficient development workflow.

There's so much more you can do with GitHub, and you have a solid start. Now...[what will you learn next](https://lab.github.com/courses)?

I won't respond to this issue, just close it when you are done!

No file, test, or implementation entry point is identified. The issue is a course-completion message that explicitly asks the recipient to close it; done means closing the issue rather than making a repository change.

Written by the indexing model from the issue text.