Skip to content

Commit b59a33c

Browse files
authored
Merge pull request #63 from configcat/contributing
contributing
2 parents 2b4b763 + f3d2eec commit b59a33c

File tree

3 files changed

+80
-1
lines changed

3 files changed

+80
-1
lines changed

CONTRIBUTING.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Contributing to the ConfigCat SDK for Elixir
2+
3+
ConfigCat SDK is an open source project. Feedback and contribution are welcome. Contributions are made to this repo via Issues and Pull Requests.
4+
5+
## Submitting bug reports and feature requests
6+
7+
The ConfigCat SDK team monitors the [issue tracker](https://github.com/configcat/elixir-sdk/issues) in the SDK repository. Bug reports and feature requests specific to this SDK should be filed in this issue tracker. The team will respond to all newly filed issues.
8+
9+
## Submitting pull requests
10+
11+
We encourage pull requests and other contributions from the community.
12+
- Before submitting pull requests, ensure that all temporary or unintended code is removed.
13+
- Be accompanied by a complete Pull Request template (loaded automatically when a PR is created).
14+
- Add unit or integration tests for fixed or changed functionality.
15+
16+
When you submit a pull request or otherwise seek to include your change in the repository, you waive all your intellectual property rights, including your copyright and patent claims for the submission.
17+
18+
In general, we follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr)
19+
20+
1. Fork the repository to your own Github account
21+
2. Clone the project to your machine
22+
3. Create a branch locally with a succinct but descriptive name
23+
4. Commit changes to the branch
24+
5. Following any formatting and testing guidelines specific to this repo
25+
6. Push changes to your fork
26+
7. Open a PR in our repository and follow the PR template so that we can efficiently review the changes.
27+
28+
## Build instructions
29+
30+
Install [Elixir](https://elixir-lang.org) development environment.
31+
32+
To install dependencies:
33+
34+
```bash
35+
mix local.rebar --force
36+
mix local.hex --force
37+
mix deps.get
38+
```
39+
40+
## Running tests
41+
42+
```bash
43+
mix test
44+
```

DEPLOY.md

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# Steps to deploy
2+
## Preparation
3+
1. Install dependencies
4+
```bash
5+
mix local.rebar --force
6+
mix local.hex --force
7+
mix deps.get
8+
```
9+
1. Run tests
10+
```bash
11+
mix coveralls.json
12+
```
13+
2. Increase the project version in `mix.exs`.
14+
4. Commit & Push
15+
## Publish
16+
Use the **same version** for the git tag as in `mix.exs`.
17+
- Via git tag
18+
1. Create a new version tag.
19+
```bash
20+
git tag v[MAJOR].[MINOR].[PATCH]
21+
```
22+
> Example: `git tag v1.0.1`
23+
2. Push the tag.
24+
```bash
25+
git push origin --tags
26+
```
27+
- Via Github release
28+
29+
Create a new [Github release](https://github.com/configcat/elixir-sdk/releases) with a new version tag and release notes.
30+
31+
## Elixir Package
32+
Make sure the new version is available on [hex.pm](https://hex.pm/packages/configcat).
33+
34+
## Update samples
35+
Update and test sample apps with the new SDK version.

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ https://configcat.com/support
8989

9090
## Contributing
9191

92-
Contributions are welcome.
92+
Contributions are welcome. For more info please read the [Contribution Guideline](CONTRIBUTING.md).
9393

9494
## About ConfigCat
9595

0 commit comments

Comments
 (0)