Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

Commit

Permalink
Merge pull request #124 from moip/develop
Browse files Browse the repository at this point in the history
[RELEASE] v4.2.0
  • Loading branch information
mbnakaya authored May 9, 2018
2 parents 81f6966 + de088e3 commit 0911841
Showing 30 changed files with 1,887 additions and 891 deletions.
24 changes: 24 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,27 @@
<a name="v4.2.0"></a>
# [](https://github.com/moip/moip-sdk-java/compare/v4.1.1...v4.2.0) (2018-05-02)


### Bug Fixes

* **Client**: apply fixes to JSON translation ([bf40270]())

### Refactor

* **Account**: fix account treatment ([4d50db3]())

### Docs

* **Readme**
* Adding slack link ([2ff4443]())
* complete and translate the documentation ([d3b63b5]())

* **Examples**
* adds request examples for all SDK features ([95e6a0a]())

* **Contributing**: adds CONTRIBUTING.md ([c2b2de5]())


<a name="v4.1.1"></a>
# [](https://github.com/moip/moip-sdk-java/compare/v4.1.0...v4.1.1) (2018-03-02)

38 changes: 38 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Contributing
:clap::tada: Thank you for taking the time to contribute! :tada::clap:

We really value your willingness to contribute to this project. In order to higher the chances of your contribution being accepted, please refer to the following guidelines!

## Steps

1. Fork it!
2. Create your feature branch: `git checkout -b feature/xyz develop`.
3. Commit your changes according to our commit message standards: `git commit -m 'feat(xyz): Added new functionality'`.
4. Push to your repo: `git push origin feature/xyz`.
5. Submit a pull request to `develop`!

## Workflow
This repo uses Gitflow as its branch management system. You can learn more about Gitflow [here](https://www.atlassian.com/git/tutorials/comparing-workflows#gitflow-workflow).
A few quick tips:
* All feature branches should be based on `develop` and have the format `feature/branch_name`.
* Minor bug fixes should be based on `master` and have the format `hotfix/branch_name`.

### Commit Conventions
In order to make the changelog generation easier we recommend the use of messages based on [Conventional Commits](https://conventionalcommits.org/).

Examples:
```
feat(orders): added `XYZ` helper function
commit description
footer notes
```

```
refactor(orders): refactored `ABC` helper function
The behaviour of `ABC` was inconsistent and (...)
BREAKING CHANGE: return type of `ABC` is now `String`
```

```
docs: updated documentation in README.md
```
Loading

0 comments on commit 0911841

Please sign in to comment.