Skip to content

Add site maintenance content #3

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.

Sign up for GitHub

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

Open
sales wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add site maintenance content #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2ba43f0
Add site maintenance section to the table of contents
sales Jul 1, 2016
b1ed187
Add Site Maintenance section
sales Jul 1, 2016
0a2e965
Add Site Maintenance section
sales Jul 1, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ Guides for getting things done, programming well, and programming in style.
* [Git](/style/git)
* [Ruby](/style/ruby)
* [Rails](/style/rails)
* [Site Maintenance](/style/site-maintenance)

## High level guidelines:

Expand Down
57 changes: 57 additions & 0 deletions style/site-maintenance/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
# Site Maintenance

## Feature
* Make sure your repository is updated
* Create a new branch from develop called `feature/feature_name`
* Add your modifications in our CHANGELOG.md file, e.g.:
```
## [1.5.0] - 2015-12-03
### Added
Feature name
```
* Every new feature will increase the `MINOR` number in the: `MAJOR.MINOR.PATCH` format. (We follow these rules)
* Run the server to check if everything is fine, push your branch and submit a new pull request
* Update the task informing people everything is ok and get at least 3 approval from the developers in your pull request to develop branch
* Merge your pull request and delete your branch
* Check and test it on our staging environment
* Merge develop into master and deploy to Heroku

## Found bugs?

* Create a new task in our project
* Try to give us all the information you have, e.g.: print screen, browser name/version, operational system, desktop/mobile version.
* Post on the **#site-startae** channel that you found a bug and registered on Flow.

## Bugfix

* Make sure your repository is updated
* Create a new branch from develop called `fix/something`
* Add your modifications in our CHANGELOG.md file, e.g.:
```
## [1.4.1] - 2015-12-03
### Changed
Bug fix
```
* Every new bugfix will increase the `PATCH` number in the: `MAJOR.MINOR.PATCH` format. (We follow these rules)
* Run the server to check if everything is fine, push your branch and submit a new pull request
* Update the task informing people everything is ok and get at least 2 approval from the developers in your pull request to develop branch
* Merge your pull request and delete your branch
* Check and test it on our staging environment
* Merge develop into master and deploy to Heroku

## Update gems and libs

* Make sure your repository is updated
* Create a new branch from develop called `feature/update_gems`
* Add your modifications in our CHANGELOG.md file, e.g.:
```
## [1.5.0] - 2015-12-03
### Changed
Update Gemfile (middleman, middleman-livereload, sass)
```
* The updates will increase the `MINOR` number in the: `MAJOR.MINOR.PATCH` format. (We follow these rules)
* Run the server to check if everything is fine, push your branch and submit a new pull request
* Update the task informing people everything is ok and get at least 1 approval from the developers in your pull request to develop branch
* Merge your pull request and delete your branch
* Check and test it on our staging environment
* Merge develop into master and deploy to Heroku