-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add link of repo #222
Comments
can you assign me for this? |
@robin6717 please make seperate pull requests for every issue solved |
Hi,
I just made a PR for 1 issue ( added a link to the repo on the main page ), and now I want to work on the other issue that i was asssigned ( change the loose sound ).
But I have a question, how do I make a separate PR when the earlier changes I made ( the added link ) are in my repo alrdy?
Sorry to bother you with this question but maybe you do not mind me asking.
I could make a new repo and clone that one but I wonder if this is the way to do it. it seems not..
Thank you for your patience and feedback!
Robin
…________________________________
Van: Aatmaj ***@***.***>
Verzonden: zaterdag 22 oktober 2022 05:48
Aan: Aatmaj-Zephyr/Hangman ***@***.***>
CC: Robin van Steenbergen ***@***.***>; Mention ***@***.***>
Onderwerp: Re: [Aatmaj-Zephyr/Hangman] Add link of repo (Issue #222)
@robin6717<https://github.com/robin6717> please make seperate pull requests for every issue solved
—
Reply to this email directly, view it on GitHub<#222 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXKP7A7NAO4VTXGR36DRDB3WENPYVANCNFSM6AAAAAARJZLLBU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
You can wait till your earlier pr gets accepted. Or your can make a new branch in your repo |
Hi, I see the link has been removed. I would love to make a new one if needed. |
I suppose it was giving an issue in mobile site.... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add link of this repo in the website
The text was updated successfully, but these errors were encountered: