<commit_before># elzar
resmio glamourous style guide  

We are publishing this styleguide as a bower package so we can require it in any
app. The styleguide is already registered as a Bower package called elzar, so
to install it on a project you need to run `bower install elzar --save` (if you
don't have bower installed run `npm install bower -g` to install it, if you
don't have npm install [Node](https://nodejs.org))  
When we have changes that we want to push to the places where elzar is used we
need to do some work. This is how it goes.  
![](http://futurama-madhouse.net/fanart/kylem/elzar2_091004.png)  

##How to work with elzar##
This is just a workflow I just came up with, so feel free to point any
error/improvement.  
1. Clone elzar by doing `git clone <EMAIL>:resmio/elzar.git`  
2. Run `cd elzar` to enter the elzar folder repo  
3. Create a branch with your feature name (`git checkout -b your-feature-name`)  
4. Run `gulp watch` to start the compiling process, it will automatically open
a browser pointing to index.html, every time you change the code gulp will
update the files and refresh the browser. If this doesn't happen check the
terminal for error messages. You need chrome canary installed since it is the
browser that gulp will open by default.  
5. Create your awesome feature, once finished run `git add -A` to tell git that
you want all the changes included in your commit, then run `git commit` to save
all your changes in a commit, it will open a text editor enter here a message
describing what your changes are for (ie: Styled the headers to use Comic Sans
and adding a blink effect to the links), save the text file and your changes
are commited.  
6. Push your branch to github `git push origin your-branch-name`.  
7. Go to the [elzar repo on github](https://github.com/resmio/elzar) and do a
pull request. This means that you want your changes integrated into the master
elzar branch. [Here](https://help.github.com/articles/creating-a-pull-request/)
is an explanation on how to create a pull request.   
8. Celebrate!  

##How to update the test your changes to elzar in the main app##
Sometimes you will want to preview the changes on the app, before making the
pull request, to do this you must have your branch pushed to the elzar github
repo (do until step 6 from the previous section). Then:  
1. Go to the app that is requiring the elzar bower package and open its
bower.json file.  
2. Under dependencies look for elzar it should be something like:
`"elzar": "0.0.9"`  
3. Change the "0.0.9" part to `"<EMAIL>:resmio/elzar.git#your-branch"`
4. Run bower install from the terminal  
5. Test your new stuff in the main app, after checking that everything is
allright continue from step 6 in the previous section.  

##How to update the bower package##
Best to do this when the branch is tested and the feature is merged into
master, but we can do it from any branch. Here's how to do it:  
1. In elzar open bower.json and look for the field called 'version', after it
you will see a number (ie: 0.0.7), update that number (we use [semantic
versioning](http://semver.org/))  
2. Update that number in package.json too (to the same version number)
3. Add and commit the changes.   
4. Tag the release by running `git tag -a v0.0.2`  
5. Push the tags to github `git push origin master --tags`  
6. Don't forget to update bower.json in the places where you use elzar.  

(You can also tag the release directly from
[github](https://help.github.com/articles/creating-releases/))  <commit_msg>FIx spaces in README.md again<commit_after># elzar
resmio glamourous style guide  

We are publishing this styleguide as a bower package so we can require it in any
app. The styleguide is already registered as a Bower package called elzar, so
to install it on a project you need to run `bower install elzar --save` (if you
don't have bower installed run `npm install bower -g` to install it, if you
don't have npm install [Node](https://nodejs.org))  
When we have changes that we want to push to the places where elzar is used we
need to do some work. This is how it goes.  


![](http://futurama-madhouse.net/fanart/kylem/elzar2_091004.png)  

##How to work with elzar##
This is just a workflow I just came up with, so feel free to point any
error/improvement.  
1. Clone elzar by doing `git clone <EMAIL>:resmio/elzar.git`  
2. Run `cd elzar` to enter the elzar folder repo  
3. Create a branch with your feature name (`git checkout -b your-feature-name`)  
4. Run `gulp watch` to start the compiling process, it will automatically open
a browser pointing to index.html, every time you change the code gulp will
update the files and refresh the browser. If this doesn't happen check the
terminal for error messages. You need chrome canary installed since it is the
browser that gulp will open by default.  
5. Create your awesome feature, once finished run `git add -A` to tell git that
you want all the changes included in your commit, then run `git commit` to save
all your changes in a commit, it will open a text editor enter here a message
describing what your changes are for (ie: Styled the headers to use Comic Sans
and adding a blink effect to the links), save the text file and your changes
are commited.  
6. Push your branch to github `git push origin your-branch-name`.  
7. Go to the [elzar repo on github](https://github.com/resmio/elzar) and do a
pull request. This means that you want your changes integrated into the master
elzar branch. [Here](https://help.github.com/articles/creating-a-pull-request/)
is an explanation on how to create a pull request.   
8. Celebrate!  

##How to update the test your changes to elzar in the main app##
Sometimes you will want to preview the changes on the app, before making the
pull request, to do this you must have your branch pushed to the elzar github
repo (do until step 6 from the previous section). Then:  
1. Go to the app that is requiring the elzar bower package and open its
bower.json file.  
2. Under dependencies look for elzar it should be something like:
`"elzar": "0.0.9"`  
3. Change the "0.0.9" part to `"<EMAIL>:resmio/elzar.git#your-branch"`  
4. Run bower install from the terminal  
5. Test your new stuff in the main app, after checking that everything is
allright continue from step 6 in the previous section.  

##How to update the bower package##
Best to do this when the branch is tested and the feature is merged into
master, but we can do it from any branch. Here's how to do it:  
1. In elzar open bower.json and look for the field called 'version', after it
you will see a number (ie: 0.0.7), update that number (we use [semantic
versioning](http://semver.org/))  
2. Update that number in package.json too (to the same version number)  
3. Add and commit the changes.   
4. Tag the release by running `git tag -a v0.0.2`  
5. Push the tags to github `git push origin master --tags`  
6. Don't forget to update bower.json in the places where you use elzar.  

(You can also tag the release directly from
[github](https://help.github.com/articles/creating-releases/))  
{'fraction_non_alphanumeric': 0.06748379825302903, 'fraction_numerical': 0.011270780501549732, 'mean_word_length': 3.758042895442359, 'pattern_counts': {'":': 2, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1706479', 'n_tokens_mistral': 2137, 'n_tokens_neox': 2017, 'n_words': 1160}