#############################################################################################
Esse é um projeto de automação de teste WEB com RobotFramework
#############################################################################################
Polisticas de Git
Criação de Branch: Padronização para Branch [bugfix|feature|config]/description Um commit por projeto e feature
Padronização de Commit: Todos podem enviar contribuição para melhoria desse processo.
[TagName]: Short description summarize in around 80 columns
Body of explanation, explaning the motivation use the rule `what` and `why`, not the how.
Resolves: #Task-ID
<Author-Signature>
The TagName should follow the pattern listed below:
[Chore]: Used to designate update a build task, configs, no production code change
[Docs]: Change documentation
[Feat]: Used to designate a new Feature
[Fix]: A bug fix
[Refactor]: User to designate a production code refactoring
[Style]: Formatting , missing semi colons, etc, no code change
[Tests]: Add tests, refactoring tests, no production code changes
Padronização para o Pull Request Commit message: [TagName]: Short description summarize in around 80 columns
Body of explanation, explaning the motivation use the rule `what` and `why`, not the how.
Resolves: #Task-ID
<Author-Signature>
Checklist sugerido para o code review: # Verificar a mensagem de commit se está de acordo com o project guide. # Verificar o Code Style # Verificar a semântica do código, nome de variável, nome do método, verificar se está de acordo com a funcionalidade # Verificar a lógica do código ## Não realizar revisão com pressa, o processo de code review leva tempo mas garante ganho de qualidade.
#############################################################################################