TerribleDev/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'taylor-projects-git' of https://github.com/stoplightio/docs into taylor-projects-git

Browse Source
This commit is contained in:
Taylor Barnett
2018-04-10 17:00:51 -05:00
parent e4448b79b5 53da0d12c1
commit ec74e0e88c
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
articles/projects/git.md
View File

@@ -1,9 +1,9 @@
# Git Repositories
## What
The Stoplight Platform is built on top of Git. This means that all your projects are Git repositories and that our platform benefits from all the additonal functionality provided by Git. To access the Git funtionality, you can use Access Tokens to access the Stoplight API, authenticate Prism in a continuous integration enviornment, and access the underlying Git repositories for projects.
The Stoplight Platform is built on top of Git. This means that all your projects are Git repositories and that our platform benefits from all the additonal functionality provided by Git. To access the Git funtionality, you will need to clone your Git repository by generating an Access Token.
> You can make this part of your Git workflow, add it to scripts, or your CI/CD process
> You can also use Access Tokens to access the Stoplight API, authenticate Prism in a continuous integration enviornment, and access the underlying Git repositories for projects. You can make this part of your Git workflow, add it to scripts, or your CI/CD process
## Who
@@ -17,15 +17,16 @@ If you have read access to a project, you will be able to:
## How to Clone Your Stoplight Git Repository
1. Under the Settings section in your Stoplight account, find the “Access Tokens” section.
1. Select the **Settings** tab on the platform homepage
2. Select **Access Tokens** from the left
![Access Tokens](https://github.com/stoplightio/docs/blob/develop/assets/images/access-tokens.png?raw=true)
2. Create a token to access projects that your Stoplight account has proper permissions for. These permissions match the ones in the Stoplight UI.
3. Create a token to access projects that your Stoplight account has proper permissions for (These permissions match the ones in the Stoplight UI)
> You can name your token whatever you want. Once you have created the token, copy it, and only store it in a safe location. Once you close the window, you will not see it again.
> You can name your token whatever you want. Once you have created the token, copy it, and only store it in a safe location. Once you close the window, you will not see it again
3. Store your access token as an environmental variable (recommended)
3. On your machine, store your access token as an environmental variable (recommended)
For example, on Mac/Linux:
@@ -45,9 +46,9 @@ For example:
git clone https://taylor:$STOPLIGHT_TOKEN@git.stoplight.io/taylor/test-new.git
```
5. If the project is associated with an organization and not a personal project, replace `username` with `organization-name`
> If the project is associated with an organization and not a personal project, replace `username` with `organization-name`
6. Now you can make changes to your files, commit, and push to your master branch. You can see these changes in the Stoplight UI as well as the "History of Changes"
5. Now you can make changes to your files, commit, and push to your master branch. You can see these changes in the Stoplight UI as well as the "History of Changes"
> Remember: You will only see changes on the master branch in the UI at this time.