\hypertarget{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23174}{}\doxysection{Questions}\label{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23174}
Please ask support questions on \href{http://stackoverflow.com/questions/tagged/webdriver-manager}{\texttt{ Stack\+Overflow}} or \href{https://gitter.im/angular/webdriver-manager}{\texttt{ Gitter}}.

Any questions posted to webdriver-\/manager\textquotesingle{}s Github Issues will be closed with this note\+:

Please direct general support questions like this one to an appropriate support channel, see \href{https://github.com/angular/webdriver-manager/blob/master/CONTRIBUTING.md\#questions}{\texttt{ https\+://github.\+com/angular/webdriver-\/manager/blob/master/\+CONTRIBUTING.\+md\#questions}}. Thank you!\hypertarget{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23175}{}\doxysection{Issues}\label{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23175}
If you have a bug or feature request, please file an issue. When submitting an issue, please include a reproducible case that we can actually run.

Please format code and markup in your issue using \href{https://help.github.com/articles/github-flavored-markdown}{\texttt{ github markdown}}.\hypertarget{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23176}{}\doxysection{Contributing to Source Code (\+Pull Requests)}\label{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23176}
Loosely, follow the \href{https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md}{\texttt{ Angular contribution rules}}.


\begin{DoxyItemize}
\item If your PR changes any behavior or fixes an issue, it should have an associated test.
\item New features should be general and as simple as possible.
\item Breaking changes should be avoided if possible.
\item All pull requests require review. No PR will be submitted without a comment from a team member stating LGTM (Looks good to me).
\end{DoxyItemize}\hypertarget{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23177}{}\doxysubsection{Webdriver-\/manager specific rules}\label{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23177}

\begin{DoxyItemize}
\item Java\+Script style should generally follow the \href{http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml}{\texttt{ Google JS style guide}}.
\item Wrap code at 100 chars.
\item Document public methods with jsdoc.
\item Be consistent with the code around you!
\end{DoxyItemize}\hypertarget{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23178}{}\doxysubsection{Commit Messages}\label{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23178}
Please write meaningful commit messages -\/ they are used to generate the changelog, so the commit message should tell a user everything they need to know about a commit. Webdriver-\/manager follows Angular\+JS\textquotesingle{}s \href{https://docs.google.com/a/google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit\#heading=h.z8a3t6ehl060}{\texttt{ commit message format}}.

In summary, this style is \begin{DoxyVerb}<type>(<scope>): <subject>
<BLANK LINE>
<body>
\end{DoxyVerb}
 Where {\ttfamily $<$type$>$} is one of \mbox{[}feat, fix, docs, refactor, test, chore, deps\mbox{]} and {\ttfamily $<$scope$>$} is a quick descriptor of the location of the change, such as cli, client\+Side\+Scripts, element.\hypertarget{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23179}{}\doxysubsection{Testing your changes}\label{md_sfcode_node_modules_protractor_node_modules_webdriver_manager_CONTRIBUTING_autotoc_md23179}
Test your changes on your machine by running {\ttfamily npm test} to run the test suite.

When you submit a PR, tests will also be run on the Continuous Integration environment through Travis. If your tests fail on Travis, take a look at the logs -\/ if the failures are known flakes in Internet Explorer or Safari you can ignore them, but otherwise Travis should pass. 