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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update github-desktop-tutorial for Github Desktop 1.0 #624

Closed
Lubits opened this Issue Oct 2, 2017 · 16 comments

Comments

4 participants
@Lubits
Contributor

Lubits commented Oct 2, 2017

Update github-desktop-tutorial.md to reflect the new Github Desktop 1.0 client.

馃悶 Problem
Github Desktop 1.0 was announced on September 19. The new version includes quite a few changes in UI compared to the version in github-desktop-tutorial.md

馃幆 Goal
Make it easier for (new) users with Github Desktop 1.0 and above following the tutorial.

馃挕 Possible solutions
Update the text and screenshots in github-desktop-tutorial.md for Github Desktop 1.0

馃搵 Steps to solve the problem

  • Comment below about what you've started working on.
  • Add, commit, push your changes
  • Submit a pull request and add this in comments - Addresses #<put issue number here>
  • Ask for a review in comments section of pull request
  • Celebrate your contribution to this project 馃帀
@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Oct 2, 2017

Collaborator

Thank you for creating this issue @Lubits.

We'd like to entertain users of old version too.
Do you wanna start working on this or the community to take this up?

Collaborator

Roshanjossey commented Oct 2, 2017

Thank you for creating this issue @Lubits.

We'd like to entertain users of old version too.
Do you wanna start working on this or the community to take this up?

@Lubits

This comment has been minimized.

Show comment
Hide comment
@Lubits

Lubits Oct 2, 2017

Contributor

@Roshanjossey I can start working on it. However, if you'd still like to keep entertaining users of the old version, would it be an idea to create a new .md file for Github Desktop 1.0?

Contributor

Lubits commented Oct 2, 2017

@Roshanjossey I can start working on it. However, if you'd still like to keep entertaining users of the old version, would it be an idea to create a new .md file for Github Desktop 1.0?

@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Oct 2, 2017

Collaborator

@Lubits, can you gimme a brief idea about what the changes will be?

Yes, let's create another .md file, make the new one as default and put a link to the old one from new one with some text Follow this if you're using a version of GitHub desktop older than 1.0

Collaborator

Roshanjossey commented Oct 2, 2017

@Lubits, can you gimme a brief idea about what the changes will be?

Yes, let's create another .md file, make the new one as default and put a link to the old one from new one with some text Follow this if you're using a version of GitHub desktop older than 1.0

@Lubits

This comment has been minimized.

Show comment
Hide comment
@Lubits

Lubits Oct 3, 2017

Contributor

@Roshanjossey The new .md file will contain the same steps but with screenshots of the new Github Desktop UI with altered text (e.g. "click on the + on the top left." is no longer true, will be replaced with something like "Press File in the menu bar and click on Clone Repository").

The README.md should then be updated to point to the new .md file.

Contributor

Lubits commented Oct 3, 2017

@Roshanjossey The new .md file will contain the same steps but with screenshots of the new Github Desktop UI with altered text (e.g. "click on the + on the top left." is no longer true, will be replaced with something like "Press File in the menu bar and click on Clone Repository").

The README.md should then be updated to point to the new .md file.

@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Oct 3, 2017

Collaborator

@Lubits, Sounds good. Go ahead. Also, make sure you have a link to the old one from the new one.

Collaborator

Roshanjossey commented Oct 3, 2017

@Lubits, Sounds good. Go ahead. Also, make sure you have a link to the old one from the new one.

@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Oct 14, 2017

Collaborator

@Lubits, any update on this? Are you stuck somewhere or need help?

Collaborator

Roshanjossey commented Oct 14, 2017

@Lubits, any update on this? Are you stuck somewhere or need help?

@Lubits

This comment has been minimized.

Show comment
Hide comment
@Lubits

Lubits Oct 16, 2017

Contributor

@Roshanjossey I've not had a lot of time this past two weeks sadly. So, if anyone wants to pick this up, be my guest. However, I'm still open to working on it (at a possible slower pace) if there's no one else.

Contributor

Lubits commented Oct 16, 2017

@Roshanjossey I've not had a lot of time this past two weeks sadly. So, if anyone wants to pick this up, be my guest. However, I'm still open to working on it (at a possible slower pace) if there's no one else.

@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Oct 16, 2017

Collaborator

@Lubits, take your time. Just checking to see if I can assist in any way

Collaborator

Roshanjossey commented Oct 16, 2017

@Lubits, take your time. Just checking to see if I can assist in any way

@stephaniemdavis

This comment has been minimized.

Show comment
Hide comment
@stephaniemdavis

stephaniemdavis Mar 28, 2018

Contributor

@Lubits @Roshanjossey - i can work on #624. Does it make sense to call the new md file "Github Desktop 1.0 Tutorial.md"?

Contributor

stephaniemdavis commented Mar 28, 2018

@Lubits @Roshanjossey - i can work on #624. Does it make sense to call the new md file "Github Desktop 1.0 Tutorial.md"?

@Lubits

This comment has been minimized.

Show comment
Hide comment
@Lubits

Lubits Mar 28, 2018

Contributor

@stephaniemdavis Great, you can go ahead! As for the filename, I don't really mind. Maybe wait for @Roshanjossey

Contributor

Lubits commented Mar 28, 2018

@stephaniemdavis Great, you can go ahead! As for the filename, I don't really mind. Maybe wait for @Roshanjossey

@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Mar 28, 2018

Collaborator

@stephaniemdavis, thank you for picking this up. I think it's better to name the the updated version as github-desktop-tutorial.md. You could change the current one as github-desktop-old-version-tutorial.md and add a link in the new version to point to old version with some text like If you're using a version of GitHub desktop before 1.0, refer this tutorial

It makes more sense to have new version as the default one.

Collaborator

Roshanjossey commented Mar 28, 2018

@stephaniemdavis, thank you for picking this up. I think it's better to name the the updated version as github-desktop-tutorial.md. You could change the current one as github-desktop-old-version-tutorial.md and add a link in the new version to point to old version with some text like If you're using a version of GitHub desktop before 1.0, refer this tutorial

It makes more sense to have new version as the default one.

@stephaniemdavis

This comment has been minimized.

Show comment
Hide comment
@stephaniemdavis

stephaniemdavis Mar 29, 2018

Contributor
Contributor

stephaniemdavis commented Mar 29, 2018

@stephaniemdavis

This comment has been minimized.

Show comment
Hide comment
@stephaniemdavis

stephaniemdavis Mar 30, 2018

Contributor

@Roshanjossey Another question: If u assign me to this task, does it then show up in my fork (along with this line of conversation) so that I can follow it? I want to create a new branch in my fork and work on it but still have access to this comment thread (#624) within my new branch.

Contributor

stephaniemdavis commented Mar 30, 2018

@Roshanjossey Another question: If u assign me to this task, does it then show up in my fork (along with this line of conversation) so that I can follow it? I want to create a new branch in my fork and work on it but still have access to this comment thread (#624) within my new branch.

@Roshanjossey

This comment has been minimized.

Show comment
Hide comment
@Roshanjossey

Roshanjossey Mar 30, 2018

Collaborator

@stephaniemdavis, GitHub doesn't have a feature to move conversations like that between forks.

You can still follow this conversation here though. You won't loose access to it if you create another branch in your fork

Collaborator

Roshanjossey commented Mar 30, 2018

@stephaniemdavis, GitHub doesn't have a feature to move conversations like that between forks.

You can still follow this conversation here though. You won't loose access to it if you create another branch in your fork

@cheriannet

This comment has been minimized.

Show comment
Hide comment
@cheriannet

cheriannet May 12, 2018

Contributor

@Roshanjossey I have updated the desktop tutorial and have sent a pull request #4368 . Please take a look and give me any feedback.

Contributor

cheriannet commented May 12, 2018

@Roshanjossey I have updated the desktop tutorial and have sent a pull request #4368 . Please take a look and give me any feedback.

@cheriannet

This comment has been minimized.

Show comment
Hide comment
@cheriannet

cheriannet May 16, 2018

Contributor

@Roshanjossey This issue can be closed. Since the pull request #4368 has been merged.

Contributor

cheriannet commented May 16, 2018

@Roshanjossey This issue can be closed. Since the pull request #4368 has been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment