-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d693303
commit 4cb113b
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
layout: layouts/get-started.njk | ||
title: GitHub and Heroku | ||
tags: | ||
- getStarted | ||
--- | ||
|
||
Storing your prototype kit code securely and using Heroku to run prototypes for testing with users. | ||
|
||
## Setting up Git | ||
|
||
You first need to follow the NHS prototype guidance on [setting up Git](https://prototype-kit.service-manual.nhs.uk/how-tos/git). | ||
|
||
## Storing your code in GitHub | ||
|
||
Prototypes should be stored as repositories in the [GitHub NHS Digital](https://github.com/NHSDigital) organisation account. | ||
|
||
Guidance on how to [get access to GitHub NHS Digital organisation](https://nhs.sharepoint.com/:u:/r/sites/X26_EngineeringCOE/SitePages/GitHub-User---how-to-request-access.aspx?csf=1&web=1&e=7WzUKB) is on SharePoint. | ||
|
||
### Naming your prototype in GitHub | ||
|
||
You should name your prototype to prevent people getting confused with production services. Use `nhsapp-prototype-` followed by the name of your service, for example: `nhsapp-prototype-prescriptions` |