-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community Exchange Introduction/Tracking #12
Comments
@PragatiVerma18, I noticed that Of course if |
Hey @ericdrosado, @rajat2502 has filled up the airtable form for submitting this repo to Community Exchange. Can you please check it once? |
I've added @rajat2502 to the list of users who will receive access to the private beta. @PragatiVerma18 and @rajat2502 you will both be added as private beta users when the invitation is extended. 🎉 |
Thanks a lot @ericdrosado 😄 |
@PragatiVerma18 @rajat2502 you are all set. Thank you for completing the issues. Early next week, I will extend an invite to you to submit your repository to CX. Please keep this issue open for now. |
Thanks @ericdrosado for all the help and support, looking forward to the CX invitation. 😄 |
@PragatiVerma18 @rajat2502 you have been given access to Community Exchange @PragatiVerma18 you will be sent an email with instructions. |
👋 Hi @PragatiVerma18,
I am your GitHub mentor for the GitHub Education, Community Exchange (CX) project. I'll be collaborating with you on preparing your repo for CX.
You mentioned in your submission that you wanted to submit a
Learn + Collaborate
repo. This means that you would like to teach students, step by step, how to build this project as well as invite other students to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for aLearn + Collaborate
CX submission on June 1, 2022.This issue will serve as a tracking issue to track all issues related to CX. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
Your repo is currently in great shape, so I don't believe we will have to do too much to get your repo ready for a CX submission 😄
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you
Issues
The text was updated successfully, but these errors were encountered: