Skip to content
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

Improve setting-up.md documentation #8920 #8939

Merged
merged 8 commits into from
Jul 6, 2018
Merged

Improve setting-up.md documentation #8920 #8939

merged 8 commits into from
Jul 6, 2018

Conversation

cybersol795
Copy link
Contributor

Fixes #8920
Typos and grammatical errors are removed and some sentence structures have slightly changed in some sections. Please review the revisions and if there is any change that you don't approve please leave me a comment. Thank you!

p.s., if you approve, after this issue is closed, I will create ~3 more issues for a few other documentation files in the repository (but will create and close them one by one)

Copy link
Member

@tshradheya tshradheya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nits. Looks good otherwise

@@ -1,14 +1,14 @@
# Setting up a development environment

This is a step-by-step guide to setting up a development environment in your local machine.
You will use that environment to work on features, enhancements, bug fixes, etc. which ultimately allows you to contribute to the project.
This is a step-by-step guide for setting up a development environment in your local machine.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on your local machine?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, "on your local machine" makes more sense.


1. Add a remote name (e.g `upstream`) for the main repo for your repo to keep in sync with, and then fetch the remote-tracking branches from the main repo.
1. Add a remote name (e.g upstream) for your copy of the main repo. Fetch the remote-tracking branches from the main repo to keep it in sync with your copy.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep the ` around upstream as its a special word in this context

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed the single quotes. Will change it.

@tshradheya tshradheya added the s.Ongoing The PR is being worked on by the author(s) label Jul 5, 2018
@@ -46,7 +46,7 @@ More information can be found at [this documentation](https://help.github.com/ar
1. Install Google Cloud SDK. Follow the directions given [here](https://cloud.google.com/sdk/downloads).
Note that you *do not* need to [initialize the SDK](https://cloud.google.com/sdk/docs/initializing).
```sh
# This command is to be run at the Google Cloud SDK directory
# Execute this command at the Google Cloud SDK directory
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets keep this consistent with line 61.

Change to Run the following command

Copy link
Member

@tshradheya tshradheya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🎉

@tshradheya tshradheya requested a review from damithc July 6, 2018 06:09
@tshradheya tshradheya self-assigned this Jul 6, 2018
@tshradheya tshradheya added s.FinalReview The PR is ready for final review and removed s.Ongoing The PR is being worked on by the author(s) labels Jul 6, 2018
@tshradheya tshradheya added s.ToMerge The PR is approved by all reviewers including final reviewer; ready for merging e.1 and removed s.FinalReview The PR is ready for final review labels Jul 6, 2018
@tshradheya tshradheya added this to the V6.7.0 milestone Jul 6, 2018
@tshradheya tshradheya changed the title improve setting-up.md documentation #8920 Improve setting-up.md documentation #8920 Jul 6, 2018
@tshradheya tshradheya merged commit 33a11a2 into TEAMMATES:master Jul 6, 2018
@tshradheya
Copy link
Member

Thanks for the contribution @cybersol795 . Looking forward to the future PR's which aim to improve the documentation.

Also in future please create a new branch and then create a PR from that :)

@cybersol795
Copy link
Contributor Author

@tshradheya I don't seem to have the permissions to check out a new branch on Teammates. My changes are on a non-master branch on my fork but the PR that I create can only be merged into one of the existing branches. Any ideas?

@tshradheya
Copy link
Member

When creating a PR, create it from the non-master branch of your fork to master of TEAMMATES fork

@xpdavid xpdavid added the c.DevOps Process-related or build-related improvement and addition label Jul 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c.DevOps Process-related or build-related improvement and addition s.ToMerge The PR is approved by all reviewers including final reviewer; ready for merging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

improve setting-up.md documentation
4 participants